public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/35471] libgfortran fails with nonstandard <complex.h>
Date: Sat, 05 Apr 2008 22:21:00 -0000	[thread overview]
Message-ID: <20080405222027.16020.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35471-15753@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from fxcoudert at gcc dot gnu dot org  2008-04-05 22:20 -------
(In reply to comment #11)
> binutils-2.9.5.0.22-6

Too old. And, with the configure line you indicated (i.e. not specifying a
special assembler and linker), it is going to be used. So, you need to use more
recent binutils. (2.13.1 was released almost 6 years ago.)

> BUT ... the configure output seems to indicate that the build as and ld used
> here are NOT the system's (unless something devious that I am missing is going
> on)...

Are you talking about the use of
/usr2/local/src/gcc-4.3-20080204/gcc-linux/./gcc/as? I think it's a symbol link
to the system "as" (or a short script calling said system "as"). It's a bit
misleading, but it's due to the way the build system works to be relocatable.

> AND the bug report cited (10877) seems to indicate that a runtime error
> results, not the linker error seen here.

But PR10877 just mentions the first time a newer binutils was required. After
that, once it we require binutils >= 2.13.1, we can use all the new features in
that version without keeping track of them (because we're then garanteed to
have it present, it's a build requirement).


-- 


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


  parent reply	other threads:[~2008-04-05 22:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 11:28 [Bug fortran/35471] New: gfortran build fails in libgfortran george at gcc dot gnu dot org
2008-03-05 21:46 ` [Bug fortran/35471] libgfortran fails with nonstandard <complex.h> fxcoudert at gcc dot gnu dot org
2008-03-11 12:03 ` [Bug libfortran/35471] " pinskia at gcc dot gnu dot org
2008-03-21 21:50 ` george at gcc dot gnu dot org
2008-03-21 21:52 ` pinskia at gcc dot gnu dot org
2008-03-22 10:38 ` george at gcc dot gnu dot org
2008-03-22 13:56 ` fxcoudert at gcc dot gnu dot org
2008-04-01  8:24 ` george at gcc dot gnu dot org
2008-04-01 10:44 ` fxcoudert at gcc dot gnu dot org
2008-04-05  8:20 ` george at gcc dot gnu dot org
2008-04-05  9:27 ` fxcoudert at gcc dot gnu dot org
2008-04-05 21:50 ` george at gcc dot gnu dot org
2008-04-05 22:21 ` fxcoudert at gcc dot gnu dot org [this message]
2008-12-23 19:40 ` jb at gcc dot gnu dot 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=20080405222027.16020.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).