qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libcacard: add libcacard.la target
Date: Mon, 16 May 2011 21:06:02 +0300	[thread overview]
Message-ID: <20110516180602.GD3868@playa.redhat.com> (raw)
In-Reply-To: <4DD13833.2050506@redhat.com>

On Mon, May 16, 2011 at 04:44:03PM +0200, Paolo Bonzini wrote:
> On 05/16/2011 07:37 PM, Alon Levy wrote:
> >I've settled on libtool
> >as the linker solution since it seems to be the de facto standard, please
> >correct me on this point if I'm wrong. We are not using autoconf, so
> >I've called it directly in it's various modes, compile, link and install.
> 
> I agree.  I don't dislike this particularly :) if at all.
> 
> >Legitemacy of the warning: basically libtool is concerned about linking in position
> >dependant code. But the trace-dtrace.o contains no .rodata section and is not actually
> >a problem for the linker, I've verfied the resulting library works fine with spicec (the
> >spice client using it).
> 
> I'm not sure, however, that glibc would still keep the sharing of .text.
> 

I'll check.

> >I'd appreciate any suggestion of a replacement for libtool if it is not appropriate.
> >Note that this building of a shared library is not something new - we've talked about
> >this before in relation to libcacard inclusion inside qemu git repository.
> 
> Do you really need tracing besides as a dependency of qemu_malloc?
> Perhaps you can recompile qemu-malloc.o specially for libcacard, and
> force usage of the nop backend.

Sounds like a very good idea for short term. Otoh if I'm already building libcacard
with qemu dependencies, it would be nice if I could benefit from the tracing framework.

I'll investigate building trace-dtrace.lo and if this doesn't work I'll try nop backend.

> 
> Paolo
> 

  reply	other threads:[~2011-05-16 15:06 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
2011-05-16 17:37                       ` Alon Levy
2011-05-16 14:44                         ` Paolo Bonzini
2011-05-16 18:06                           ` Alon Levy [this message]
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=20110516180602.GD3868@playa.redhat.com \
    --to=alevy@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).