| 1 |
Paul de Vrieze posted <200602281553.53803.pauldv@g.o>, excerpted |
| 2 |
below, on Tue, 28 Feb 2006 15:53:53 +0100: |
| 3 |
|
| 4 |
> These particular files are the default pieces of code that gcc in |
| 5 |
> executable linking mode automatically adds to your executables (not your |
| 6 |
> shared libraries). They take care that your "C" system behaves as you |
| 7 |
> expect it to. They do things such as setting up the system in such a way |
| 8 |
> that main gets called correctly, libraries are initialised, etc. As this |
| 9 |
> code is common for all C files, gcc just links in these files instead of |
| 10 |
> generating them all the time. |
| 11 |
|
| 12 |
Indeed. I was wrong. Seems I have those particular *.o files in lib64 as |
| 13 |
well. Learned something new 2day! =8^) |
| 14 |
|
| 15 |
-- |
| 16 |
Duncan - List replies preferred. No HTML msgs. |
| 17 |
"Every nonfree program has a lord, a master -- |
| 18 |
and if you use the program, he is your master." Richard Stallman in |
| 19 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-amd64@g.o mailing list |
Archives