public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug gcov-profile/40433] New: /usr/bin/ld: cannot open crti.o: No such file or directory
@ 2009-06-13 1:28 ksong at lbl dot gov
2009-06-13 1:55 ` [Bug gcov-profile/40433] " pinskia at gcc dot gnu dot org
0 siblings, 1 reply; 2+ messages in thread
From: ksong at lbl dot gov @ 2009-06-13 1:28 UTC (permalink / raw)
To: gcc-bugs
Hi, I got the error of
/usr/bin/ld: cannot open crti.o: No such file or directorycollect2: ld returned
1 exit status
make[2]: *** [32/libgcc_s.so] Error 1
make[1]: *** [stmp-multilib] Error 2
make: *** [all-gcc] Error 2
I actually have the crti.o file at /usr/lib64/
Don't know how to setup the library path to let "make" find crti.o
I have tried
export PATH=/usr/lib64/:${PATH}
export LD_LIBRARY_PATH=/usr/lib64/:${LD_LIBRARY_PATH}
export LDFLAGS=-L/usr/lib64/
export LIBS=-l/usr/lib64/
Also, my configuration is like this:
../gcc-4.0.4/configure --prefix=/home/software/gcc/4.0.4/
My gcc version is 3.2.3 .
Could you please help with me?
Thanks a lot!
Kai
--
Summary: /usr/bin/ld: cannot open crti.o: No such file or
directory
Product: gcc
Version: 4.0.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ksong at lbl dot gov
GCC host triplet: Fail to compile on Centos-3.4, Don't know how to setup
the libra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40433
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-06-13 1:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-06-13 1:28 [Bug gcov-profile/40433] New: /usr/bin/ld: cannot open crti.o: No such file or directory ksong at lbl dot gov
2009-06-13 1:55 ` [Bug gcov-profile/40433] " pinskia at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).