This is the mail archive of the gcc-bugs@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]

[Bug bootstrap/35752] [4.3/4.4 Regression]: Combined gcc + binutils source tree doesn't bootstrap



------- Comment #32 from oblivian at users dot sourceforge dot net  2008-04-01 18:55 -------
(In reply to comment #30)
> This patch should work.  It creates a good collect-ld for me.
> 

How about a simple change without the whole fast-install patch.

    if test -x $scriptdir/../prev-$dir/$prog; then
      exec $scriptdir/../prev-$dir/$prog ${1+"$@"}
    else
      exec $scriptdir/../$dir/$prog ${1+"$@"}
    fi

Thats it.  Just prefer the use of the previous stage utilities. No worrying
about the state of the current stage utilities.  Unless I'm missing something
(e.g. internal gcc reasons) doesn't this meet the primary requirement
bootstrapping the compiler (i.e. building the current stage with the previous)
and prevents mixing partially finished utilities inside the stage?
It also keeps the exec-tool.in script clean from specialized code depending on
the target it's being run as (well except for the invoke case statement at the
top).

I'm currently through stage 2 with this simple change to exec-tool.in.

As long as this doesn't break any rules, it should allow the sysroot problems I
had to disappear as well, which will fix my prefix issue as well.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35752


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