I am porting NewLib for my own OS by following a tutorial.
It says that once I finished my crt0, I have to “link it as the first object”. How can I do that?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
That means precisely what is says. When an application for your OS is being linked, the crt0 must be the very first object file on linker’s command line: before any other object file.
Traditionally, UNIX linkers resolve a symbol by making a look up starting from first object/library looping over to the last object/library. Putting
crt0as the first object file makes sure that system symbols (functions, variables) are picked from the crt0 file, not some other file.Additionally, as pointed by R.., traditional linkers assume that application’s entry point is at the beginning of the code segment. That also fits to the source code found on the linked page: first symbol in the code is
_start, the usual name of the program’s entry point.E.g. running
gcc -v a.c -o aon my Debian (notice the-v), one sees following linking command (I have added new lines for readability):One can see that crt1 is first object on the command line. Looking at the linker script (
-m elf_i386->find /usr -name '*elf_i386*'-> on my system/usr/lib/ldscripts/elf_i386.x) one can verify that on Linux there is nocrt0, but there are:crt1,crti,crtbegin,crtend,crtn. And the application object files (/tmp/ccndJ4YV.oin the sample above) are put between thecrtbeginandcrtend.