From: "John Calcote" <jcalcote@novell.com>
To: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>,
binutils@sourceware.org
Subject: Re: linker error with new linker
Date: Wed, 12 Jul 2006 17:04:00 -0000 [thread overview]
Message-ID: <44B4D72A.37FF.0081.0@novell.com> (raw)
In-Reply-To: <200607121846.03794@enterprise.flameeyes.is-a-geek.org>
Deigo,
Thank you!
This was exactly what I was looking for. I had already considered the idea of adding -fPIC to my CFLAGS for the static libraries, but immediately threw that out as a "hack". ;-)
John
>>> Diego 'Flameeyes' Pettenò <flameeyes@gentoo.org> 7/12/2006 10:45 AM >>>
On Wednesday 12 July 2006 18:27, John Calcote wrote:
> However, the real question was: Does anyone know if there's a
> "standard" way of dealing with the "linking shared libraries from static
> libraries in autotools" issue?
You have to build them with -fPIC, or simply use libtool, declare them as
noinst_LTLIBRARIES, and libtool will take care of it linking them entirely
inside the shared libraries using the PIC version.
Some packages ships with a libfoo_p.a archive built with PIC, too.
--
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is ( http://farragut.flameeyes.is/ )-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
next prev parent reply other threads:[~2006-07-12 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:28 John Calcote
2006-07-12 16:46 ` Diego 'Flameeyes' Pettenò
2006-07-12 17:04 ` John Calcote [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 5:08 John Calcote
2006-07-12 14:08 ` Daniel Jacobowitz
2006-07-12 15:32 ` Andreas Jaeger
2006-07-12 16:17 ` İsmail Dönmez
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=44B4D72A.37FF.0081.0@novell.com \
--to=jcalcote@novell.com \
--cc=binutils@sourceware.org \
--cc=flameeyes@gentoo.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).