public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "oblivian at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/35752] [4.3/4.4 Regression]: Combined gcc + binutils source tree doesn't bootstrap Date: Mon, 31 Mar 2008 23:10:00 -0000 [thread overview] Message-ID: <20080331230939.436.qmail@sourceware.org> (raw) In-Reply-To: <bug-35752-682@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from oblivian at users dot sourceforge dot net 2008-03-31 23:09 ------- I am convinced that the patch is almost certainly wrong, is not the root cause of the problem, and the 4.3.0 implementation of libtool is almost certainly broken. While the patch allows the compiler to be built in phase 2 and complete, it is pulling in libraries from the host system. 4.2.3 Most certainly did not. I'm looking at build logs from both versions and for example the 4.2.3 build configure log for phase 2 showed that it could not find libflex -lfl for all stages of the build, where as 4.3.0 can't find -lfl in stage 1 and in stage 2 and follow it all of a sudden starts finds it. Since flex is not installed until after the phase 2 toolchain it should not be found by the compiler if it is searching /tools/lib for the whole bootstrap build. Beyond this bfd in stage 2 of the phase 2 compiler is showing sys_lib_search_path_spec with /lib and /usr/lib in it, which is very bad for the phase 2 compiler I'm trying to build. I'm going to start looking into where sys_lib_search_path_spec is set and find the deltas between the two versions since I'm not sure where else to look. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35752
next prev parent reply other threads:[~2008-03-31 23:10 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-28 22:23 [Bug bootstrap/35752] New: " hjl dot tools at gmail dot com 2008-03-29 1:48 ` [Bug bootstrap/35752] " hjl dot tools at gmail dot com 2008-03-31 17:44 ` hjl dot tools at gmail dot com 2008-03-31 17:48 ` [Bug bootstrap/35752] [4.3/4.4 Regression]: " hjl dot tools at gmail dot com 2008-03-31 17:54 ` bonzini at gnu dot org 2008-03-31 18:17 ` hjl dot tools at gmail dot com 2008-03-31 20:30 ` oblivian at users dot sourceforge dot net 2008-03-31 22:27 ` rwild at gcc dot gnu dot org 2008-03-31 23:10 ` oblivian at users dot sourceforge dot net [this message] 2008-03-31 23:26 ` oblivian at users dot sourceforge dot net 2008-04-01 7:09 ` bonzini at gnu dot org 2008-04-01 10:25 ` oblivian at users dot sourceforge dot net 2008-04-01 11:22 ` bonzini at gnu dot org 2008-04-01 11:52 ` oblivian at users dot sourceforge dot net 2008-04-01 11:54 ` bonzini at gnu dot org 2008-04-01 11:57 ` oblivian at users dot sourceforge dot net 2008-04-01 12:09 ` bonzini at gnu dot org 2008-04-01 12:15 ` oblivian at users dot sourceforge dot net 2008-04-01 12:34 ` bonzini at gnu dot org 2008-04-01 12:41 ` oblivian at users dot sourceforge dot net 2008-04-01 13:49 ` bonzini at gnu dot org 2008-04-01 13:54 ` oblivian at users dot sourceforge dot net 2008-04-01 15:31 ` oblivian at users dot sourceforge dot net 2008-04-01 15:37 ` bonzini at gnu dot org 2008-04-01 15:40 ` oblivian at users dot sourceforge dot net 2008-04-01 15:42 ` Ralf dot Wildenhues at gmx dot de 2008-04-01 15:42 ` bonzini at gnu dot org 2008-04-01 15:42 ` oblivian at users dot sourceforge dot net 2008-04-01 15:50 ` hjl dot tools at gmail dot com 2008-04-01 15:51 ` hjl dot tools at gmail dot com 2008-04-01 16:12 ` bonzini at gnu dot org 2008-04-01 16:45 ` oblivian at users dot sourceforge dot net 2008-04-01 18:56 ` oblivian at users dot sourceforge dot net 2008-04-01 19:04 ` oblivian at users dot sourceforge dot net 2008-04-01 19:05 ` oblivian at users dot sourceforge dot net 2008-04-02 10:08 ` [Bug bootstrap/35752] [4.3/4.4 Regression]: Combined gcc + binutils source tree doesn't bootstrap with --enable-shared bonzini at gnu dot org 2008-04-02 10:09 ` bonzini at gcc dot gnu dot org 2008-04-02 13:48 ` oblivian at users dot sourceforge dot net 2008-04-02 14:00 ` bonzini at gnu dot org 2008-04-02 14:20 ` oblivian at users dot sourceforge dot net 2008-04-21 13:37 ` hjl dot tools at gmail dot com 2008-04-21 13:54 ` bonzini at gnu dot org 2008-04-21 14:02 ` hjl dot tools at gmail dot com 2008-04-21 14:08 ` bonzini at gnu dot org 2008-04-21 14:13 ` Ralf dot Wildenhues at gmx dot de 2008-04-21 14:27 ` hjl dot tools at gmail dot com 2008-04-21 14:39 ` bonzini at gnu dot org 2008-04-21 14:40 ` bonzini at gnu dot org 2008-04-21 15:53 ` hjl dot tools at gmail dot com 2008-04-21 16:06 ` bonzini at gnu dot org 2008-04-21 16:19 ` hjl dot tools at gmail dot com 2008-04-21 16:26 ` bonzini at gnu dot org 2008-04-21 16:40 ` hjl dot tools at gmail dot com 2008-04-21 17:03 ` bonzini at gnu dot org 2008-04-22 5:28 ` Ralf dot Wildenhues at gmx dot de 2008-04-22 6:27 ` bonzini at gnu dot org 2008-04-22 17:52 ` Ralf dot Wildenhues at gmx dot de 2008-04-25 15:01 ` oblivian at users dot sourceforge dot net 2008-04-25 15:21 ` bonzini at gnu dot org 2008-06-11 11:11 ` jsm28 at gcc dot gnu dot org 2008-06-13 21:55 ` mmitchel at gcc dot gnu dot org 2008-07-31 12:46 ` bonzini at gnu dot org 2008-08-01 8:28 ` [Bug bootstrap/35752] [4.3 " bonzini at gnu dot org 2008-08-01 9:53 ` bonzini at gcc dot gnu dot org 2008-08-04 12:25 ` bonzini at 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=20080331230939.436.qmail@sourceware.org \ --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).