public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michaud.bernard@ic.gc.ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/10802] Bootstrap of gcc-3.3 on Solaris 9 x86 fails on undefined symbol in libgcj.so Date: Tue, 03 Jun 2003 19:42:00 -0000 [thread overview] Message-ID: <20030603194212.2070.qmail@sources.redhat.com> (raw) In-Reply-To: <20030515132600.10802.michaud.bernard@ic.gc.ca> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10802 ------- Additional Comments From michaud.bernard@ic.gc.ca 2003-06-03 19:42 ------- Subject: RE: Bootstrap of gcc-3.3 on Solaris 9 x86 f ails on undefined symbol in libgcj.so Sorry for the delay in answering Dara, things here have been quite hectic... The gcc 3.2.3 compiler (the version doing the compiling) is installed in /opt/gcc-3.2.3, and I was trying to build gcc 3.3 to /opt/gcc-3.3. However, I may have found the cause of the original problem. I found symbolic links pointing from /usr/local/lib to an older version of gcc-3.2, as such: libgcc_s.so -> libgcc_s.so.1 libgcc_s.so.1 -> /opt/gcc-3.2.1/lib/libgcc_s.so.1 This is possibly what is responsible for the build picking up the wrong version of libgcc, as /usr/local/lib was in my search path. Regards, Bernard Michaud ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2003-06-03 19:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030515132600.10802.michaud.bernard@ic.gc.ca> 2003-05-26 7:17 ` dhazeghi@yahoo.com 2003-05-26 13:09 ` michaud.bernard@ic.gc.ca 2003-05-26 17:37 ` dhazeghi@yahoo.com 2003-05-26 17:45 ` pinskia@physics.uc.edu 2003-05-26 18:10 ` michaud.bernard@ic.gc.ca 2003-05-27 6:52 ` dhazeghi@yahoo.com 2003-05-27 11:41 ` michaud.bernard@ic.gc.ca 2003-05-27 15:21 ` pinskia@physics.uc.edu 2003-06-03 19:42 ` michaud.bernard@ic.gc.ca [this message] 2003-06-08 3:51 ` dhazeghi@yahoo.com 2003-07-12 3:39 ` neroden 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=20030603194212.2070.qmail@sources.redhat.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).