From: Rob Browning <rlb@cs.utexas.edu>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com, drepper@gnu.ai.mit.edu (Ulrich Drepper)
Subject: Re: Shared library linking problem.
Date: Tue, 28 Oct 1997 19:00:00 -0000 [thread overview]
Message-ID: <87hga1i80n.fsf@nevermore.csres.utexas.edu> (raw)
In-Reply-To: <m0xQNNQ-0004edC@ocean.lucon.org>
hjl@lucon.org (H.J. Lu) writes:
> I heard this once with Qt. Which glibc 2 are you using? I have
> no problem with the slightly older glibc 2.1 on x86 and glibc
> 2.0.5c on alpha.
Apologies all around, the problem's solved. It turned out someone
here had accidentally deleted -fPIC in a dark corner of our bloated
Makefile.
Sorry for the false alarm.
--
Rob Browning <rlb@cs.utexas.edu>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30
next prev parent reply other threads:[~1997-10-28 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-28 15:21 Rob Browning
1997-10-28 17:57 ` H.J. Lu
1997-10-28 18:29 ` Marc Lehmann
1997-10-28 18:44 ` H.J. Lu
1997-10-28 19:00 ` Ulrich Drepper
1997-10-29 5:13 ` Neal Becker
1997-10-28 19:00 ` Rob Browning [this message]
1997-10-29 5:13 ` Neal Becker
1997-10-29 16:16 ` H.J. Lu
1997-10-29 19:23 ` Neal Becker
1997-10-30 20:10 ` H.J. Lu
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=87hga1i80n.fsf@nevermore.csres.utexas.edu \
--to=rlb@cs.utexas.edu \
--cc=drepper@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).