public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Jean-pierre dot vial at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/29867]  New: building libgfortran fails because of multiple definitions gcc-4.3-20061111
Date: Thu, 16 Nov 2006 08:51:00 -0000	[thread overview]
Message-ID: <bug-29867-9295@http.gcc.gnu.org/bugzilla/> (raw)

linking libgfortran fails becaus of multiple definitions.
Here are le last lines of error messages. there are several hundred such lines

/usr/include/stdlib.h:342: multiple definition of `strtoul'
.libs/environ.o:/usr/include/stdlib.h:342: first defined here
.libs/in_unpack_generic.o: In function `strtol':
/usr/include/stdlib.h:336: multiple definition of `strtol'
.libs/environ.o:/usr/include/stdlib.h:336: first defined here
.libs/in_unpack_generic.o: In function `strtod':
/usr/include/stdlib.h:330: multiple definition of `strtod'
.libs/environ.o:/usr/include/stdlib.h:330: first defined here
.libs/in_unpack_generic.o: In function `atoi':
/usr/include/stdlib.h:403: multiple definition of `atoi'
.libs/environ.o:/usr/include/stdlib.h:403: first defined here
.libs/in_unpack_generic.o: In function `strtol':
/usr/include/stdlib.h:336: multiple definition of `atol'
.libs/environ.o:/usr/include/stdlib.h:336: first defined here
.libs/in_unpack_generic.o: In function `strtoll':
/usr/include/stdlib.h:384: multiple definition of `atoll'
.libs/environ.o:/usr/include/stdlib.h:384: first defined here
.libs/in_unpack_generic.o: In function `strtod':
/usr/include/stdlib.h:330: multiple definition of `atof'
.libs/environ.o:/usr/include/stdlib.h:330: first defined here
collect2: ld returned 1 exit status
make[3]: *** [libgfortran.la] Erreur 1

This problem did not exist in the previous edition of gcc-4.3
it is new in 20061111


-- 
           Summary: building libgfortran fails because of multiple
                    definitions gcc-4.3-20061111
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Jean-pierre dot vial at wanadoo dot fr
 GCC build triplet: host-x86_64-unknown-linux-gnu
  GCC host triplet: host-x86_64-unknown-linux-gnu
GCC target triplet: host-x86_64-unknown-linux-gnu


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


             reply	other threads:[~2006-11-16  8:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16  8:51 Jean-pierre dot vial at wanadoo dot fr [this message]
2006-11-16 11:50 ` [Bug libfortran/29867] " rguenth at gcc dot gnu dot org
2006-11-16 15:20 ` jpvial at nerim dot net
2006-11-16 15:27 ` Jean-pierre dot vial at wanadoo dot fr
2006-11-16 15:36 ` Jean-pierre dot vial at wanadoo dot fr
2006-11-16 16:24 ` [Bug libfortran/29867] [4.3 Regression] " pinskia at gcc dot gnu dot org
2006-11-20  9:34 ` [Bug target/29867] " eesrjhc at bath dot ac dot uk
2006-11-21 17:30 ` Jean-pierre dot vial at wanadoo dot fr
2006-12-01 11:42 ` dfranke at gcc dot gnu dot org
2006-12-03  4:55 ` ron3763 at msn dot com
2006-12-03  4:58 ` ron3763 at msn dot com
2006-12-07 15:11 ` dfranke at gcc dot gnu dot org
2006-12-14 21:41 ` dfranke at gcc dot gnu dot org
2006-12-20 23:01 ` dfranke at gcc dot gnu dot org
2006-12-21  9:10 ` eesrjhc at bath dot ac dot uk
2006-12-21 21:01 ` Jean-pierre dot vial at wanadoo dot fr
2006-12-21 21:13 ` dfranke at gcc dot gnu dot org
2006-12-22 19:20 ` Jean-pierre dot vial at wanadoo dot fr
2006-12-23 17:54 ` dfranke at gcc dot gnu dot org
2007-01-02  1:14 ` eesrjhc at bath dot ac dot uk
2007-01-06 11:11 ` dfranke 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=bug-29867-9295@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).