From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libcacard: add libcacard.la target
Date: Mon, 16 May 2011 15:59:53 +0200 [thread overview]
Message-ID: <4DD12DD9.2040400@redhat.com> (raw)
In-Reply-To: <4DD12691.7080905@codemonkey.ws>
On 05/16/2011 03:28 PM, Anthony Liguori wrote:
>>
>>
>> *** Warning: Linking the shared library libcacard.la against the
>> non-libtool
>> *** objects ../trace-dtrace.o is not portable!
>
> I don't think slipping in libtool like this is such a good idea.
I disagree but, the warning is indeed legitimate, so
NACK
> Isn't la just a static archive compiled with -fPIC?
No, .la is a text file pointing (most importantly) to the static
library, the shared library, and the dependencies of the static library.
Alon, do you need this to comply with some packaging guidelines
forbidding static libraries?
Paolo
next prev parent reply other threads:[~2011-05-16 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 15:40 [Qemu-devel] [PATCH 0/2] add libcacard shared object target Alon Levy
2011-05-15 15:40 ` [Qemu-devel] [PATCH 1/2] configure: add libdir and --libdir Alon Levy
2011-05-15 15:40 ` [Qemu-devel] [PATCH 2/2] libcacard: add libcacard.la target Alon Levy
2011-05-16 7:00 ` Paolo Bonzini
2011-05-16 10:25 ` Alon Levy
2011-05-16 10:32 ` Paolo Bonzini
2011-05-16 12:06 ` Gerd Hoffmann
2011-05-16 12:07 ` Paolo Bonzini
2011-05-16 12:14 ` Alon Levy
2011-05-16 12:18 ` Paolo Bonzini
2011-05-16 13:25 ` [Qemu-devel] [PATCH] " Alon Levy
2011-05-16 13:28 ` Anthony Liguori
2011-05-16 13:59 ` Paolo Bonzini [this message]
2011-05-16 17:37 ` Alon Levy
2011-05-16 14:44 ` Paolo Bonzini
2011-05-16 18:06 ` Alon Levy
2011-05-16 17:40 ` Alon Levy
2011-05-17 12:03 ` Alon Levy
2011-05-17 12:32 ` Alon Levy
[not found] ` <20110518034240.GL7083@playa.tlv.redhat.com>
2011-05-18 7:16 ` Paolo Bonzini
2011-05-18 8:49 ` Alon Levy
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=4DD12DD9.2040400@redhat.com \
--to=pbonzini@redhat.com \
--cc=alevy@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).