public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sos at cal dot interrasystems dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/23325] New: gcc 64 bit build problem Date: Thu, 11 Aug 2005 13:32:00 -0000 [thread overview] Message-ID: <20050811133220.23325.sos@cal.interrasystems.com> (raw) Platform : AMD 64bit Opteron. O/S : Redhat linux Advanced Server 3.0 Kernel Version : 2.4.21-1.1931.2.393.ent When we try to build gcc 3.4.3, the build fails giving the following error. /usr/bin/ld: cannot open crti.o: No such file or directory collect2: ld returned 1 exit status make[2]: *** [32/libgcc_s_32.so] Error 1 make[2]: *** Waiting for unfinished jobs.... ranlib 32/libgcc.a But crti.o is present at the path /usr/lib64/crti.o -- Summary: gcc 64 bit build problem Product: gcc Version: 3.4.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sos at cal dot interrasystems dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23325
next reply other threads:[~2005-08-11 13:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-11 13:32 sos at cal dot interrasystems dot com [this message] 2005-08-11 13:33 ` [Bug target/23325] " pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050811133220.23325.sos@cal.interrasystems.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).