This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Problem building GCC
- From: Arjen Markus <arjen dot markus895 at gmail dot com>
- To: Arjen Markus <arjen dot markus895 at gmail dot com>, Fortran List <fortran at gcc dot gnu dot org>
- Date: Fri, 1 Jul 2011 14:39:37 +0200
- Subject: Re: Problem building GCC
- References: <BANLkTimiPJ+Gnw6_UbT9VdnX3BvHg2AcOw@mail.gmail.com> <20110622180250.GA24963@axel> <BANLkTik8xxyuh5i2ceOyT+4D=huG_5C-Fg@mail.gmail.com> <BANLkTinkgJtuTwafQR1aS10X8BiPCbB64g@mail.gmail.com> <20110623074654.GF24963@axel> <BANLkTi=U7EEyf=RcjoZQ5wyPtcj4TOf3ew@mail.gmail.com> <BANLkTi=VXBDdk58QhAB1oY9yywqUXUxBvw@mail.gmail.com> <20110624071006.GF10903@axel> <BANLkTin8TDQ6HjpoWRzwfs8VaF2OO+zVpw@mail.gmail.com> <BANLkTi=GQ9jRGTFTx2ciLbi6VqTfcEmVTQ@mail.gmail.com> <BANLkTimz=QoPq=DP_S17QihWh-3K=af2hg@mail.gmail.com>
Hello,
Eric Botcazou concluded from all this mishap that the make utility under MinGW
was to blame. However, when I tried to build it on a Linux machine, I got this
error message:
make[3]: Leaving directory `/u/markus/tmp/gcc4.6.1/build-gcc/gcc'
mkdir -p -- x86_64-unknown-linux-gnu/libgcc
Checking multilib configuration for libgcc...
Configuring stage 1 in x86_64-unknown-linux-gnu/libgcc
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for x86_64-unknown-linux-gnu-ar... ar
checking for x86_64-unknown-linux-gnu-lipo... lipo
checking for x86_64-unknown-linux-gnu-nm...
/u/markus/tmp/gcc4.6.1/build-gcc/./gcc/nm
checking for x86_64-unknown-linux-gnu-ranlib... ranlib
checking for x86_64-unknown-linux-gnu-strip... strip
checking whether ln -s works... yes
checking for x86_64-unknown-linux-gnu-gcc...
/u/markus/tmp/gcc4.6.1/build-gcc/./gcc/xgcc
-B/u/markus/tmp/gcc4.6.1/build-gcc/./gcc/
-B/u/markus/tmp/gcc4.6.1.bin/x86_64-unknown-linux-gnu/bin/
-B/u/markus/tmp/gcc4.6.1.bin/x86_64-unknown-linux-gnu/lib/ -isystem
/u/markus/tmp/gcc4.6.1.bin/x86_64-unknown-linux-gnu/include -isystem
/u/markus/tmp/gcc4.6.1.bin/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/u/markus/tmp/gcc4.6.1/build-gcc/x86_64-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/u/markus/tmp/gcc4.6.1/build-gcc'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/u/markus/tmp/gcc4.6.1/build-gcc'
make: *** [all] Error 2
I am rather surprised that all of a sudden configure runs into a problem.
Any suggestions?
Regards,
Arjen
2011/6/28 Arjen Markus <arjen.markus895@gmail.com>:
> Hello,
>
> here are the results of removing ..../gcc/ada and using a relative
> path to "configure" again:
> make now complains about Make-lang.in in .../gcc/cp - the
> target pattern contains no %.
>
> The whole problem might just be caused by an old version
> of make in the MinGW/MSYS environment I am using (GNU Make 3.81).
>
> I guess it is worth checking that out - just done that: I added a path to
> GNU Make version 3.82, but then the build fails on an unknown command "r".
>
> Nope, I am really stuck here.
>
> Regards,
>
> Arjen
>
> 2011/6/28 Arjen Markus <arjen.markus895@gmail.com>:
>> Hi Axel,
>>
>> 2011/6/28 Arjen Markus <arjen.markus895@gmail.com>:
>>> - Remove in addition the subdirectory .../gcc/ada
>>> ?-- the build failed because there was no rule for "configure",
>>> required by the target "config.status"
>>>
>>
>> Scratch that remark - that was due to the use of an _absolute_
>> path for running configure!
>