All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, Consul <void@aleksoft.net>,
	Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows runtime error
Date: Wed, 27 May 2009 17:39:31 -0500	[thread overview]
Message-ID: <4A1DC123.6070807@codemonkey.ws> (raw)
In-Reply-To: <4A190FF6.9000004@redhat.com>

Avi Kivity wrote:
> Blue Swirl wrote:
>> I disagree, whole-archive should only be used very sparingly,
>> basically for the block/* stuff only. Otherwise most emulators will be
>> linked with a lot of unnecessary objects files from the archives that
>> will never be used on that platform.
>>   
>
> I think even for block/* we should not use whole archive.  Specifying 
> the full list of objects, or perhaps a partially linked object is much 
> cleaner.

I'm not opposed to this.  I don't see a lot of advantages to using a 
static library.

Regards,

Anthony Liguori

  reply	other threads:[~2009-05-27 22:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 21:58 [Qemu-devel] Windows runtime error Consul
2009-05-22  2:11 ` Anthony Liguori
2009-05-22 12:04   ` Paul Brook
2009-05-22 13:07     ` Anthony Liguori
2009-05-22 13:15       ` Paul Brook
2009-05-22 15:48         ` Anthony Liguori
2009-05-22 16:12           ` Blue Swirl
2009-05-22 16:39             ` Anthony Liguori
2009-05-22 15:55         ` Blue Swirl
2009-05-22 16:36           ` Anthony Liguori
2009-05-24  9:14           ` Avi Kivity
2009-05-27 22:39             ` Anthony Liguori [this message]
2009-05-22 15:51   ` Blue Swirl
2009-05-22 16:35     ` Anthony Liguori
2009-05-22 16:53       ` Blue Swirl
2009-05-22 17:15         ` Paul Brook

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=4A1DC123.6070807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=void@aleksoft.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.