From: Matt <matt@use.net>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: bootstrap comparison failure with bootstrap-lto
Date: Fri, 18 Nov 2011 21:08:00 -0000 [thread overview]
Message-ID: <Pine.NEB.4.64.1111181204040.14521@cesium.clock.org> (raw)
In-Reply-To: <mcrd3cqoshc.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
On Thu, 17 Nov 2011, Ian Lance Taylor wrote:
> Matt <matt@use.net> writes:
>
>> It *kind of* says why. I've pasted the output below. Unfortunately,
>> when the full build is finished, the prev-gcc/xgcc no longer
>> exists. When I test the conftest.c (copied and pasted from the log),
>> the stage1-gcc/xgcc and stage2-gcc/xgcc have no problem with it (of
>> course).
>
> OK, if this works after the build is complete, then you are going to
> need to stop the build in the middle. Fortunately, this can be done
> easily enough by running "make configure-stage2-gcc". That should stop
> after the stage2-gcc directory is configured. At that point, you should
> see a stage2-gcc directory and a prev-gcc directory. Presumably the
> stage2-gcc/config.log file will show a failure, and with luck you will
> be able to recreate that failure at that point.
Do I need to run a complete build first? When I run that make target right
after configure, it fails in multiple ways when building from r181491:
matt@matt-desktop:~/src/gcc-trunk/obj$ ../configure --enable-bootstrap
--prefix=/home/matt --enable-clocale=gnu --with-system-zlib
--enable-shared --with-demangler-in-ld --enable-lto
--with-build-config=bootstrap-lto --with-fpmath=sse
--enable-languages=c,c++,lto
[...]
matt@matt-desktop:~/src/gcc-trunk/obj$ make configure-stage2-gcc
make[1]: Entering directory `/home/matt/src/gcc-trunk/obj'
mv: cannot stat `stage1-gcc': No such file or directory
make[1]: *** [stage2-start] Error 1
make[1]: Leaving directory `/home/matt/src/gcc-trunk/obj'
make: *** [configure-stage2-lto-plugin] Error 2
matt@matt-desktop:~/src/gcc-trunk/obj$ make configure-stage2-gcc
mkdir -p -- ./lto-plugin
Configuring stage 2 in ./lto-plugin
configure: creating cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for x86_64-unknown-linux-gnu-gcc...
/home/matt/src/gcc-trunk/obj/./prev-gcc/xgcc
-B/home/matt/src/gcc-trunk/obj/./prev-gcc/
-B/home/matt/x86_64-unknown-linux-gnu/bin/
-B/home/matt/x86_64-unknown-linux-gnu/bin/
-B/home/matt/x86_64-unknown-linux-gnu/lib/ -isystem
/home/matt/x86_64-unknown-linux-gnu/include -isystem
/home/matt/x86_64-unknown-linux-gnu/sys-include
checking for C compiler default output file name...
configure: error: in `/home/matt/src/gcc-trunk/obj/lto-plugin':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** [configure-stage2-lto-plugin] Error 77
Weird.
By the way, thanks for taking the time to help me work through debugging
this issue so I can file a meaningful bug. I really appreciate it :)
--
tangled strands of DNA explain the way that I behave.
http://www.clock.org/~matt
next prev parent reply other threads:[~2011-11-18 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 22:23 Matt
2011-11-15 5:56 ` Ian Lance Taylor
2011-11-16 21:55 ` Matt
2011-11-17 5:43 ` Ian Lance Taylor
2011-11-18 6:35 ` Matt
2011-11-18 13:47 ` Ian Lance Taylor
2011-11-18 21:08 ` Matt [this message]
2011-11-19 1:11 ` Ian Lance Taylor
2011-11-19 2:41 ` Matt
2011-11-19 15:37 ` Ian Lance Taylor
2011-11-20 6:51 ` Matt
2011-11-20 7:32 ` Ian Lance Taylor
2011-11-20 20:23 ` Matt Hargett
2011-11-21 17:27 ` Ian Lance Taylor
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=Pine.NEB.4.64.1111181204040.14521@cesium.clock.org \
--to=matt@use.net \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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: link
Be 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).