From: Ulrich Drepper <drepper@cygnus.com>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: ld and common symbols (fwd)
Date: Tue, 21 Dec 1999 15:12:00 -0000 [thread overview]
Message-ID: <m3wvq799gx.fsf@localhost.localnet> (raw)
In-Reply-To: <m3zov39at7.fsf@localhost.localnet>
Ulrich Drepper <drepper@cygnus.com> writes:
> The linker issue in the message below seems to be preventing libc from
> building properly on my machines. What happens is that, when building
> ld.so, the common definition of __libc_multiple_libcs in dl-sysdep.os
> is no longer sufficient to stop init-first.os from being sucked into
> librtld.os.
I haven't seen a problem so far but will keep an eye on it and talk to
Nick.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1999-12-21 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E120XUA-00072S-00@kings-cross.london.uk.eu.org>
[not found] ` <199912212237.OAA14550@cygnus.com>
1999-12-21 14:43 ` Ulrich Drepper
1999-12-21 15:12 ` Ulrich Drepper [this message]
2000-01-19 1:23 ` NIIBE Yutaka
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=m3wvq799gx.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--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).