Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
Jamfile | H A D | 05-Nov-2024 | 1.2 KiB | 34 | 29 | |
generate_stubs.py | H A D | 13-Aug-2014 | 1.9 KiB | 72 | 49 | |
libroot_stubs.c | H A D | 22-Jul-2024 | 75.7 KiB | 2,808 | 2,804 | |
libroot_stubs.c.readme | H A D | 13-Aug-2014 | 884 | 20 | 14 | |
libroot_stubs_legacy.c | H A D | 22-Jul-2024 | 71.8 KiB | 2,790 | 2,786 | |
libroot_stubs_sparc.c | H A D | 22-Dec-2021 | 804 | 52 | 50 | |
libroot_stubs_x86.c | H A D | 05-Nov-2024 | 26 | 2 | 1 |
libroot_stubs.c.readme
1The source file libroot_stubs.c contains empty stubs for all symbols exported by 2libroot.so, including definitions of all versioned symbols. 3 4From libroot_stubs.c, <stubbed>libroot.so can be built, which is a stubbed 5version of libroot.so (i.e. without any code). This stubbed library is used 6during stage 0 of the bootstrap process, in order to build the gcc-syslibs 7(libgcc, libsupc++ and libstdc++). 8 9The python script generate_stubs.py can be used to regenerate libroot_stubs.c 10from a built version of (the real) libroot.so. This may be necessary when new 11symbols have been added to libroot.so. 12 13The command for regenerating libroot_stubs.c is this: 14 15 nm <path-to-libroot.so> | generate_stubs.py >libroot.stubs.c 16 17There is a separate version of the stubs file for the legacy compiler (gcc2), 18which uses a different symbol mangling format and contains the symbols for 19libgcc, too. 20