From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Multiple definition of __libc_multiple_libcs
Date: Mon, 10 Jan 2000 08:35:00 -0000 [thread overview]
Message-ID: <u8hfglubpm.fsf@gromit.rhein-neckar.de> (raw)
With the current glibc 2.2, I received the following error message:
/opt/egcs1.1.2/bin/gcc -nostdlib -nostartfiles -r -o /build-glibc-dl-wip/20000110/elf/librtld.os '-Wl,-(' /build-glibc-dl-wip/20000110/elf/dl-allobjs.os /build-glibc-dl-wip/20000110/libc_pic.a -lgcc '-Wl,-)'
/build-glibc-dl-wip/20000110/libc_pic.a(init-first.os): In function `init':
/libc-dl-wip/csu/../sysdeps/unix/sysv/linux/init-first.c:61: multiple definition of `__libc_multiple_libcs'
/build-glibc-dl-wip/20000110/elf/dl-allobjs.os(.data+0xe4):/libc-dl-wip/elf/rtld.c: first defined here
Why do we have in sysdeps/generic/dl-sysdep.c:
int __libc_multiple_libcs = 0; /* Defining this here avoids the inclusion
of init-first. */
and also in sysdeps/unix/sysv/linux/init-first.c:
/* Set nonzero if we have to be prepared for more then one libc being
used in the process. Safe assumption if initializer never runs. */
int __libc_multiple_libcs = 1;
and why is this a problem on Linux/MIPS and not on Linux/ix86? I'm a
little bit confused and appreciate your help.
Is this a bug in binutils? On Linux/MIPS I use:
$ ld --version
GNU ld 2.9.5
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
next reply other threads:[~2000-01-10 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 8:35 Andreas Jaeger [this message]
2000-01-10 9:09 ` Andreas Schwab
2000-01-24 14:46 ` Ralf Baechle
2000-01-24 23:46 ` Andreas Jaeger
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=u8hfglubpm.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=libc-hacker@sourceware.cygnus.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).