This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: crti.o: No such file

From: booleandomain <booleandomain at gmail dot com>
To: gcc-help at gcc dot gnu dot org
Date: Tue, 30 Jun 2009 16:44:44 -0700
Subject: Re: crti.o: No such file
References: <h2bbm9$uko$1@ger.gmane.org> <m3d48mzoct.fsf@google.com> <h2cgp3$g9v$1@ger.gmane.org> <h2chqo$jhv$1@ger.gmane.org> <4A49CF1A.5010804@wippies.com> <h2cjc5$seq$1@ger.gmane.org> <4A4A215F.9050809@wippies.com>

Earlier you wrote something which really doesn't fit in your scheme :

 >>> On GNU/Linux crti.o comes from glibc, not gcc.  It is normally found
 >>> in /usr/lib.
 >> On my system that file resides in /usr/lib64/crti.o.

So, where is this file, in the "native old root system" or in your new
chroot'ed self-made system?  Of course in your self-made system the
'$LFS/usr/lib64/crti.o' would be the component, from the self-made
glibc and the new chroot'ed GCC should find and use it, not the Gentoo
one in '/usr/lib64'.

When I'm chrooted, the file in in /usr/lib64/crti.o (which corresponds to $LFS/usr/lib64/crti.o outside of the chroot).

In the Gentoo Linux system, that file is in /usr/lib64/crti.o too, but I have a /usr/lib symlink pointing to /usr/lib64 so it can also be accessed as /usr/lib/crti.o.

References:
- crti.o: No such file
  - From: booleandomain
- Re: crti.o: No such file
  - From: Ian Lance Taylor
- Re: crti.o: No such file
  - From: booleandomain
- Re: crti.o: No such file
  - From: booleandomain
- Re: crti.o: No such file
  - From: Kai Ruottu
- Re: crti.o: No such file
  - From: booleandomain
- Re: crti.o: No such file
  - From: Kai Ruottu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]