From: amodra@one.net.au
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] xfree86 build problem
Date: Sun, 15 Apr 2001 15:47:43 +0930 [thread overview]
Message-ID: <20010415154649.F25145@squeak.one.net.au> (raw)
On Sat, Apr 14, 2001 at 10:36:25PM -0600, Grant Grundler wrote:
> amodra@one.net.au wrote:
> > True, but it's not recommended. The reason being that non-PIC code in
> > a shared lib will mean lib pages with relocations can't be shared between
> > processes should the library be loaded at a different virtual addresses.
>
> Well, I guess either x86 doesn't have that problem,
It does.
> no one has noticed it, or no one cares (OpenGL fans?).
Possibly :-( As Ulrich mentioned, it's fairly easy to see if a shared lib
can't actually be shared. "readelf -d libwhatever.so | grep DT_TEXTREL"
> Under build-env/xc/lib/GL/glu Imakefiles
> all have the following construct: (eg libtess/Imakefile)
>
> NormalLibraryTarget(tess, $(OBJS))
> rm -f unshared; ln -sf . ./unshared
>
> The result is only .a's get built and the libGLU.so is globbed together
> from those. The last step fails for __hppa__ since the .o's are non-PIC.
I suppose you could build the .a lib with -fPIC as a workaround.
--
Alan Modra
next reply other threads:[~2001-04-15 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 6:17 amodra [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-13 22:21 [parisc-linux] xfree86 build problem Grant Grundler
2001-04-14 11:55 ` amodra
2001-04-14 22:18 ` Grant Grundler
2001-04-14 23:00 ` Ulrich Drepper
2001-04-14 23:41 ` Alan Cox
2001-04-15 4:23 ` Grant Grundler
2001-04-15 12:32 ` Alan Cox
2001-04-15 4:42 ` amodra
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=20010415154649.F25145@squeak.one.net.au \
--to=amodra@one.net.au \
--cc=200104150436.WAA30928@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.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