Changeset 3605600 in rtems-docs for user/rsb/project-sets.rst


Ignore:
Timestamp:
Aug 12, 2019, 6:55:17 AM (5 months ago)
Author:
Vaibhav Gupta <vaibhavgupta40@…>
Branches:
master
Children:
b836c43
Parents:
fac2873
git-author:
Vaibhav Gupta <vaibhavgupta40@…> (08/12/19 06:55:17)
git-committer:
Joel Sherrill <joel@…> (08/20/19 18:44:37)
Message:

Add steps to test Newlib patch.

Update the checksum to be used for the Newlib patches.
Earlier it was msd5, but it is depreciated for security
reasons. Now RSB accepts sha512.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • user/rsb/project-sets.rst

    rfac2873 r3605600  
    262262will see the patch is present and will not attempt to download it. Once you are
    263263happy with the patch submit it to the project and a core developer will review
    264 it and add it to the RTEMS Tools git repository.  For example, to test a local
    265 patch for newlib, add the following two lines to the .cfg file in
    266 ``rtems/config/tools/`` that is included by the bset you use:
     264it and add it to the RTEMS Tools git repository.
     265
     266Testing a Newlib Patch
     267~~~~~~~~~~~~~~~~~~~~~~
     268
     269To test a local patch for newlib, you need to add the following
     270two lines to the ``.cfg`` file in ``rsb/rtems/config/tools/`` that is included
     271by the bset you use:
     272
     273.. topic:: Steps:
     274
     275  1. Create patches for the changes you want to test. (Note: For RSB, before
     276     creating Newlib patch, you must run ``autoreconf -fvi`` in the required
     277     directory after you make changes to the code. This is not required when
     278     you create patch to send to ``newlib-devel``. But if you want RSB to
     279     address your changes, your patch should also include regenerated files.)
     280
     281  2. Calculate ``sha512`` of your patch.
     282
     283  3. Place the patches in ``rsb/rtems/patches`` directory.
     284
     285  4. Open the ``.bset`` file used by your BSP in ``rsb/rtems/config``.
     286     For example, for ``rtems5``, ``SPARC``, the file will be
     287     ``rsb/rtems/config/5/rtems-sparc.bset``.
     288
     289  5. Inside it you will find the name of ``.cfg`` file for Newlib, used by
     290     your BSP.
     291     For example, I found ``tools/rtems-gcc-7.4.0-newlib-1d35a003f``.
     292
     293  6. Edit your ``.cfg`` file. In my case it will be,
     294     ``rsb/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg``. And
     295     add the information about your patch as mentioned below.
    267296
    268297.. code-block:: spec
    269298
    270     %patch add newlib file://0001-this-is-a-newlib-patch.patch  <1>
    271     %hash md5 0001-this-is-a-newlib-patch.diff 77d070878112783292461bd6e7db17fb <2>
     299    %patch add newlib -p1 file://0001-Port-ndbm.patch <1>
     300    %hash sha512 0001-Port-ndbm.patch 7d999ceeea4f3dc82e8e0aadc09d983a7a68b44470da8a3d61ab6fc558fdba6f2c2de3acc2f32c0b0b97fcc9ab799c27e87afe046544a69519881f947e7881d1 <2>
    272301
    273302.. topic:: Items:
     
    275304  1. The diff file prepended with ``file://`` to tell RSB this is a local file.
    276305
    277   2. The output from md5sum on the diff file.
     306  2. The output from sha512sum on the patch file.
Note: See TracChangeset for help on using the changeset viewer.