building/installing GCC and crtx.o's confusion

["michael.a" <wild dot eyed dot boy dot from dot freecloud at gmail dot com>]

I recently built and installed gcc (I am hacking it a little) ...and once I
got to the point of linking a library with the newly built gcc, I get this
error:

g++: /usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64/crti.o: No such
file or directory
g++: /usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64/crtn.o: No such
file or directory

The binary the distro installs from its repository is 4.0.3, but the release
I built and installed is 4.0.0.

I seriously doubt I'm managing this right. I just created some symlinks to
patch through to the new install from /usr/lib(or bin) to /usr/local/lib (I
probably should've just changed the install prefix, but I wanted to make
sure everything works first)

In any case, the trouble is, crti.o and crtn.o do exist! (as superuser)
...so I'm assuming the errors must really mean the files aren't suitable to
the new g++.

So my question boils down to I think, what exactly goes on about these crt
files after a 'make; make install'

There are crtbegin and crtend etc in the /usr/local/lib/gcc/ install
directory. I'm just not having any luck finding much info poking around
google pages.

They are the C runtime libraries obviously, but I can't seem to find any
real documentation on there organization.

-- 
View this message in context: http://www.nabble.com/building-installing-GCC-and-crtx.o%27s-confusion-tf3949291.html#a11204116
Sent from the gcc - Help mailing list archive at Nabble.com.