public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60830] [4.9 Regression] ICE on bootstrapping on cygwin
Date: Fri, 18 Apr 2014 19:37:00 -0000	[thread overview]
Message-ID: <bug-60830-4-oAeW5WxtO1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60830-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #27 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Denis Excoffier from comment #26)
> After more investigation, it seems that the culprit can be
> --disable-sjlj-exceptions. Since the beginning (last Sunday), each time i
> use it on the command line, the build fails and each time i don't use it,
> the build succeeds.
> Please would you mind trying again a cygwin build, but
> with --disable-sjlj-exceptions this time. Especially for those where the
> build succeeded. For Mikael (see comment #2), it is more than probable that
> he used --disable-sjlj-exceptions instead of my gmp kludges known by nobody
> except by me.

Yes, adding --disable-sjlj-exceptions makes the build fail:

mkdir -p -- i686-pc-cygwin/libgcc
Checking multilib configuration for libgcc...
Configuring stage 2 in i686-pc-cygwin/libgcc
configure: creating cache ./config.cache
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
xgcc: error: unrecognized command line option '-isystem'
xgcc: error: unrecognized command line option '-isystem'
xgcc: error: unrecognized command line option '-mtune=generic'
xgcc: error: unrecognized command line option '-march=pentiumpro'
checking for i686-pc-cygwin-ar... ar
checking for i686-pc-cygwin-lipo... lipo
checking for i686-pc-cygwin-nm... /home/ED/gnu/gcc-build/./gcc/nm
checking for i686-pc-cygwin-ranlib... ranlib
checking for i686-pc-cygwin-strip... strip
checking whether ln -s works... yes
checking for i686-pc-cygwin-gcc... /home/ED/gnu/gcc-build/./gcc/xgcc
-B/home/ED/gnu/gcc-build/./gcc/ -B/home/ed/gnu/install/i686-pc-cygwin/bin/
-B/home/ed/gnu/install/i686-pc-cygwin/lib/ -isystem
/home/ed/gnu/install/i686-pc-cygwin/include -isystem
/home/ed/gnu/install/i686-pc-cygwin/sys-include
checking for C compiler default output file name...
configure: error: in `/home/ED/gnu/gcc-build/i686-pc-cygwin/libgcc':
configure: error: C compiler cannot create executables
See `config.log' for more details.
Makefile:17788: recipe for target 'configure-stage2-target-libgcc' failed
make[2]: *** [configure-stage2-target-libgcc] Error 77
make[2]: Leaving directory '/home/ED/gnu/gcc-build'
Makefile:20606: recipe for target 'stage2-bubble' failed
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory '/home/ED/gnu/gcc-build'
Makefile:897: recipe for target 'all' failed
make: *** [all] Error 2


  parent reply	other threads:[~2014-04-18 19:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 10:28 [Bug bootstrap/60830] New: " gcc@Denis-Excoffier.org
2014-04-13 11:05 ` [Bug bootstrap/60830] " gcc@Denis-Excoffier.org
2014-04-13 12:33 ` mikpelinux at gmail dot com
2014-04-14  8:44 ` [Bug bootstrap/60830] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-04-14  8:45 ` rguenth at gcc dot gnu.org
2014-04-14  9:05 ` gcc@Denis-Excoffier.org
2014-04-14  9:06 ` gcc@Denis-Excoffier.org
2014-04-14  9:11 ` gcc@Denis-Excoffier.org
2014-04-14 14:16 ` jakub at gcc dot gnu.org
2014-04-14 14:42 ` gcc@Denis-Excoffier.org
2014-04-14 14:43 ` gcc@Denis-Excoffier.org
2014-04-14 17:06 ` ktietz at gcc dot gnu.org
2014-04-14 18:54 ` ktietz at gcc dot gnu.org
2014-04-15  9:35 ` gcc@Denis-Excoffier.org
2014-04-15  9:35 ` gcc@Denis-Excoffier.org
2014-04-15  9:59 ` ktietz at gcc dot gnu.org
2014-04-15 10:04 ` rguenth at gcc dot gnu.org
2014-04-15 10:31 ` ktietz at gcc dot gnu.org
2014-04-15 12:19 ` ktietz at gcc dot gnu.org
2014-04-15 16:20 ` gcc@Denis-Excoffier.org
2014-04-15 16:31 ` gcc@Denis-Excoffier.org
2014-04-15 16:50 ` gcc@Denis-Excoffier.org
2014-04-16  7:38 ` gcc@Denis-Excoffier.org
2014-04-16 12:10 ` ktietz at gcc dot gnu.org
2014-04-18 12:37 ` gcc@Denis-Excoffier.org
2014-04-18 19:37 ` bernd.edlinger at hotmail dot de [this message]
2014-04-20 19:09 ` bernd.edlinger at hotmail dot de
2014-04-21 14:02 ` bernd.edlinger at hotmail dot de
2014-04-21 16:31 ` gcc@Denis-Excoffier.org
2014-04-21 16:35 ` gcc@Denis-Excoffier.org
2014-04-21 16:50 ` bernd.edlinger at hotmail dot de
2014-04-21 17:01 ` gcc@Denis-Excoffier.org
2014-04-21 17:18 ` bernd.edlinger at hotmail dot de
2014-04-21 17:40 ` gcc@Denis-Excoffier.org
2014-04-21 17:52 ` ktietz at gcc dot gnu.org
2014-04-21 20:40 ` bernd.edlinger at hotmail dot de
2014-04-21 20:48 ` bernd.edlinger at hotmail dot de
2014-04-22  7:24 ` ktietz at gcc dot gnu.org
2014-04-22  7:29 ` bernd.edlinger at hotmail dot de
2014-04-22  7:38 ` gcc@Denis-Excoffier.org
2014-04-22 13:50 ` gcc@Denis-Excoffier.org
2014-04-27 14:10 ` mikpelinux at gmail dot com
2014-04-30 14:23 ` ktietz at gcc dot gnu.org
2014-05-02 17:36 ` fanael4 at gmail dot com
2014-05-02 19:50 ` bernd.edlinger at hotmail dot de
2014-07-13 10:34 ` gcc@Denis-Excoffier.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=bug-60830-4-oAeW5WxtO1@http.gcc.gnu.org/bugzilla/ \
    --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: 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).