public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernard at brenda-arkle dot me dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37865] gfortran build fails in stage 3 bootstrap with --enable-intermodule
Date: Sat, 13 Dec 2008 23:54:00 -0000	[thread overview]
Message-ID: <20081213235315.13253.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37865-12315@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from bernard at brenda-arkle dot me dot uk  2008-12-13 23:53 -------
I'm not sure what 'now' means.  It's still true for release 4.3.2!
I'm prepared to test with the live sources, but do you want me to?
Do you believe that the problem has been understood and addressed,
or are you hoping that it's gone away (not for the first time in
the history of gcc 4.x.x)?

The following configuration options work fine with --disable-intermodule
substituted for --enable-intermodule.

'../gcc-4.3.2/configure' '--prefix=/usr' '--libexecdir=/usr/lib'
'--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-libada'
'--enable-libssp' '--disable-werror' '--with-mpfr=/usr' '--with-gmp=/usr'
'--with-datarootdir=/usr/share' '--with-docdir=/usr/share/gcc-4.3.2/doc'
'--with-pdfdir=/usr/share/gcc-4.3.2/doc'
'--with-htmldir=/usr/share/gcc-4.3.2/doc/html' '--disable-coverage'
'--enable-nls' '--enable-__cxa_atexit' '--enable-decimal-float'
'--disable-fixed-point' '--enable-threads=posix' '--enable-clocale=gnu'
'--enable-shared' '--enable-intermodule'
'--enable-languages=ada,c++,fortran,java,objc,obj-c++,treelang,c'
'--with-local-prefix=/usr' '--with-gnu-ld' '--with-demangler-in-ld'
'--with-gnu-as' '--with-system-libunwind' '--with-system-zlib'
'--enable-bootstrap'

Configured exactly as given, the relevant bit of the build output is:

Comparing stages 2 and 3
warning: ./cc1objplus-checksum.o differs
warning: ./cc1-checksum.o differs
warning: ./cc1plus-checksum.o differs
warning: ./cc1obj-checksum.o differs
Bootstrap comparison failure!
./libbackend.o differs

That's with *almost* unmodified sources.  As it happens, as
part of working around a bug which I reported, I've adopted
two patches which have made their way into the live tree:

  (a) the patch for "my" bug 37870: the patch functionally
      changes gcc/expmed.c and adds a new test
  (b) the patch noted at
      http://gcc.gnu.org/ml/gcc-patches/2008-08/msg02201.html
      which I grabbed simply to confirm that it wasn't relevant
      (it also modifies gcc/expmed.c).

I don't believe that these changes are relevant (and in any case,
they make the 4.3.2 source more rather than less like the
current live tree).


-- 


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


  parent reply	other threads:[~2008-12-13 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 21:45 [Bug fortran/37865] New: " bernard at brenda-arkle dot me dot uk
2008-12-08 22:34 ` [Bug c/37865] " mikael at gcc dot gnu dot org
2008-12-13 23:54 ` bernard at brenda-arkle dot me dot uk [this message]
2008-12-14 14:47 ` mikael at gcc dot gnu dot org
2008-12-14 15:32 ` aldot at gcc dot gnu dot org
2008-12-14 20:31 ` bernard at brenda-arkle dot me dot uk
2008-12-15  0:15 ` mikael at gcc dot gnu dot org
2008-12-18 18:56 ` bernard at brenda-arkle dot me dot uk
     [not found] <bug-37865-4@http.gcc.gnu.org/bugzilla/>
2012-01-28 21:02 ` pinskia at gcc dot gnu.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=20081213235315.13253.qmail@sourceware.org \
    --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).