public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pierre42d at 9online dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/6560] New: Problem compiling glibc 2.7
Date: Sun, 25 May 2008 11:14:00 -0000	[thread overview]
Message-ID: <20080525111415.6560.pierre42d@9online.fr> (raw)

[...]
make[2]: Leaving directory `/tmp/glibc-2.7/elf'
cd /tmp/glibc-2.7/build &&
/usr/local/lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ar
cruv libc.a `cat csu/stamp.o iconv/stamp.o iconvdata/stamp.o locale/stamp.o
localedata/stamp.o assert/stamp.o ctype/stamp.o intl/stamp.o catgets/stamp.o
math/stamp.o setjmp/stamp.o signal/stamp.o stdlib/stamp.o stdio-common/stamp.o
libio/stamp.o dlfcn/stamp.o malloc/stamp.o string/stamp.o wcsmbs/stamp.o
timezone/stamp.o time/stamp.o dirent/stamp.o grp/stamp.o pwd/stamp.o
posix/stamp.o io/stamp.o termios/stamp.o resource/stamp.o misc/stamp.o
socket/stamp.o sysvipc/stamp.o gmon/stamp.o gnulib/stamp.o wctype/stamp.o
manual/stamp.o shadow/stamp.o po/stamp.o argp/stamp.o crypt/stamp.o nptl/stamp.o
resolv/stamp.o nss/stamp.o rt/stamp.o conform/stamp.o debug/stamp.o
glibc-libidn-2.7/stamp.o libidn/stamp.o nptl_db/stamp.o inet/stamp.o
hesiod/stamp.o sunrpc/stamp.o nis/stamp.o nscd/stamp.o streams/stamp.o
login/stamp.o elf/stamp.o stamp.o`
r - locale/C-ctype.o
r - libidn/idn-stub.o
: /tmp/glibc-2.7/build/libc.a
gcc   -nostdlib -nostartfiles -r -o /tmp/glibc-2.7/build/libc_pic.os \
 -Wl,-d -Wl,--whole-archive /tmp/glibc-2.7/build/libc_pic.a
/tmp/glibc-2.7/build/libc_pic.a(idn-stub.os): In function `__idna_to_unicode_lzlz':
idn-stub.c:(.text+0x0): multiple definition of `__idna_to_unicode_lzlz'
/tmp/glibc-2.7/build/libc_pic.a(idn-stub.os):idn-stub.c:(.text+0x0): first
defined here
/tmp/glibc-2.7/build/libc_pic.a(idn-stub.os): In function `__idna_to_ascii_lz':
idn-stub.c:(.text+0x1a0): multiple definition of `__idna_to_ascii_lz'
/tmp/glibc-2.7/build/libc_pic.a(idn-stub.os):idn-stub.c:(.text+0x1a0): first
defined here
collect2: ld returned 1 exit status
make[1]: *** [/tmp/glibc-2.7/build/libc_pic.os] Error 1
make[1]: Leaving directory `/tmp/glibc-2.7'
make: *** [all] Error 2

-- 
           Summary: Problem compiling glibc 2.7
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: pierre42d at 9online dot fr
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=6560

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-05-25 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 11:14 pierre42d at 9online dot fr [this message]
2008-05-25 16:03 ` [Bug libc/6560] " pierre42d at 9online dot fr
2008-05-25 16:56 ` drepper at redhat dot com

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=20080525111415.6560.pierre42d@9online.fr \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).