This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: building/installing GCC and crtx.o's confusion
- From: "michael.a" <wild dot eyed dot boy dot from dot freecloud at gmail dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Tue, 19 Jun 2007 17:16:14 -0700 (PDT)
- Subject: Re: building/installing GCC and crtx.o's confusion
- References: <11204116.post@talk.nabble.com>
michael.a wrote:
>
> 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
> just in case) ...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' (that is when building/installing gcc)
>
> 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.
>
>
Here is the link input:
/bin/sh ./libtool --tag=CXX --mode=link g++ -fvisibility=hidden
-fno-for-scope -fpermissive -o libMAPS.la -rpath /usr/local/lib
-version-info 0:0:0 MAPSatlas.lo MAPSdisk.lo MAPSdll.lo MAPSmap.lo MAPSys.lo
MAPSapi.lo
g++ -shared -nostdlib
/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64/crti.o
/usr/lib/gcc/x86_64-linux-gnu/4.0.3/crtbeginS.o .libs/MAPSatlas.o
.libs/MAPSdisk.o .libs/MAPSdll.o .libs/MAPSmap.o .libs/MAPSys.o
.libs/MAPSapi.o -Wl,--rpath -Wl,/usr/local/lib/../lib64 -Wl,--rpath
-Wl,/usr/local/lib/../lib64 -L/usr/lib/gcc/x86_64-linux-gnu/4.0.3
-L/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64
-L/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../.. -L/lib/../lib64
-L/usr/lib/../lib64 /usr/local/lib/../lib64/libstdc++.so -lm -lc -lgcc_s
/usr/lib/gcc/x86_64-linux-gnu/4.0.3/crtendS.o /
usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64/crtn.o -Wl,-soname
-Wl,libMAPS.so.0 -o .libs/libMAPS.so.0.0.0
make[1]: Leaving directory `/home/users/michael/dev/MAPS'
It looks a little wonky to me maybe???
--
View this message in context: http://www.nabble.com/building-installing-GCC-and-crtx.o%27s-confusion-tf3949291.html#a11205247
Sent from the gcc - Help mailing list archive at Nabble.com.