From: Roland McGrath <roland@frob.com>
To: hjl@lucon.org (H.J. Lu)
Cc: drepper@cygnus.com, libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: Re: A static, none thread patch
Date: Fri, 30 Jul 1999 07:57:00 -0000 [thread overview]
Message-ID: <199907301457.KAA14406@frob.com> (raw)
In-Reply-To: <19990730143358.3585757B9@ocean.lucon.org>
> > > * elf/dl-load.c (_dl_init_paths): Set up rtld_search_dirs only
> > > if necessary.
> >
> > If there are no system dirs something is wrong.
>
> As I said, I got it when I configured glibc as static only on ia32.
> I got
This is the bug. If you are building the elf subdir at all, even
static-only, you need a definition for this (for libdl.a to use).
The right fix is probably just to move the default-rpath definition
in Makeconfig out of the $(build-shared) conditional, since it's in fact
needed any time elf/ is built whether shared or static.
prev parent reply other threads:[~1999-07-30 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-29 10:33 H.J. Lu
1999-07-29 23:34 ` Ulrich Drepper
1999-07-30 7:35 ` H.J. Lu
1999-07-30 7:57 ` Roland McGrath [this message]
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=199907301457.KAA14406@frob.com \
--to=roland@frob.com \
--cc=drepper@cygnus.com \
--cc=hjl@lucon.org \
--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).