[Bug bootstrap/32690] New: 4.2.1 Bootstrap fails - gcc-4_2-branch/boehm-gc/ltconfig: No such file or directory

[Bug bootstrap/32690] New: 4.2.1 Bootstrap fails - gcc-4_2-branch/boehm-gc/ltconfig: No such file or directory

[rob1weld at aol dot com]

gcc version 4.2.1 20070628

make profiledbootstrap
...
Configuring in i686-pc-linux-gnu/boehm-gc
...
checking for i686-pc-linux-gnu-strip... strip
updating cache ./config.cache
/bin/sh: /root/downloads/gcc-4_2-branch/boehm-gc/ltconfig: No such file or
directory
configure: error: libtool configure failed
make[1]: *** [configure-target-boehm-gc] Error 1
make[1]: Leaving directory `/opt/gcc-4_2_1-build'
make: *** [profiledbootstrap] Error 2

A similar problem existed here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28609


This is what I did:

# ls /root/downloads/gcc-4_2-branch/boehm-gc/ltconfig
ls: /root/downloads/gcc-4_2-branch/boehm-gc/ltconfig: No such file or directory

pwd
/opt/gcc-4_2_1-build
cd /root/downloads/gcc-4_2-branch/
cp ltconfig boehm-gc
cd /opt/gcc-4_2_1-build

make profiledbootstrap

The configure scripts run and print this a few times (since I changed
NOTHING!):
/bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
...


Then this annoyance:
...
make[3]: Entering directory `/opt/gcc-4_2_1-build/libcpp'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/opt/gcc-4_2_1-build/libcpp'
make[3]: Entering directory `/opt/gcc-4_2_1-build/libdecnumber'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/opt/gcc-4_2_1-build/libdecnumber'
make[3]: Entering directory `/opt/gcc-4_2_1-build/gcc'
make[3]: Leaving directory `/opt/gcc-4_2_1-build/gcc'
make[2]: Leaving directory `/opt/gcc-4_2_1-build'
make[2]: Entering directory `/opt/gcc-4_2_1-build'
make[3]: Entering directory `/opt/gcc-4_2_1-build'
rm -f stage_current
make distclean-stagefeedback
make[4]: Entering directory `/opt/gcc-4_2_1-build'
rm -rf stagefeedback-* 
make[4]: Leaving directory `/opt/gcc-4_2_1-build'
make[3]: Leaving directory `/opt/gcc-4_2_1-build'


So it will be a few hours until I know my fix worked.
What is with this "rm -f stage_current" "make distclean-stagefeedback" stuff.
Why not just continue where I left off!


-- 
           Summary: 4.2.1 Bootstrap fails - gcc-4_2-branch/boehm-
                    gc/ltconfig: No such file or directory
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rob1weld at aol dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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

[Bug bootstrap/32690] 4.2.1 Bootstrap fails - gcc-4_2-branch/boehm-gc/ltconfig: No such file or directory

[rob1weld at aol dot com]

------- Comment #1 from rob1weld at aol dot com  2007-07-09 20:27 -------
A few hours later and it failed for want of ltcf-c.sh and ltcf-cxx.sh. I ran
gcc_update again and that fixed the configure / makefile problem of not copying
those files over.

There is still the annoyance of the build re-starting too far back and using
"rm -f stage_current" / "rm -rf stagefeedback-*" - even if you only type just
"make" (instead of "make profiledbootstrap").

It would be better if the build made it as far as the libraries then it would
not try to remake the 'use feedback' stages and simply continue the libraries
where it left off.


-- 


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

[Bug bootstrap/32690] 4.2.1 Bootstrap fails - gcc-4_2-branch/boehm-gc/ltconfig: No such file or directory

[rob1weld at aol dot com]

------- Comment #2 from rob1weld at aol dot com  2009-01-19 18:06 -------
(In reply to comment #1)
> A few hours later and it failed for want of ltcf-c.sh and ltcf-cxx.sh. I ran
> gcc_update again and that fixed the configure / makefile problem of not copying
> those files over.

I no longer get that problem with "gcc version 4.4.0 20090117 (experimental)
[trunk revision 143454]".


> There is still the annoyance of the build re-starting too far back and using
> "rm -f stage_current" / "rm -rf stagefeedback-*" - even if you only type just
> "make" (instead of "make profiledbootstrap").
> It would be better if the build made it as far as the libraries then it would
> not try to remake the 'use feedback' stages and simply continue the libraries
> where it left off.

That problem still occurs with "gcc version 4.4.0 20090117 (experimental)
[trunk revision 143454]".

Rob


-- 


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