qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sam McKelvie <sammck@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Statically Compiling including SDL
Date: Wed, 11 May 2016 13:39:45 -0700	[thread overview]
Message-ID: <C9CBEDB5-A704-4108-A36F-A6ED32CA8C9C@gmail.com> (raw)
In-Reply-To: <CAFEAcA-afAvc_E4pYouyUh9T3hYyTTQgsdNMATo79k59c8KRHw@mail.gmail.com>

Apologies for breaking the thread of the discussion; still
haven’t figured out how to cold-respond to a thread without an incoming email.

Thank you for your response. Indeed, for my purposes I only need the
static linux-user binary, so I can just remove SDL and it’s not a problem.

I’d agree that it is an SDL package distribution problem; in this case it is coming
from delian-jessie.

Thank you,
Sam McKelvie

> On May 11, 2016, at 11:30 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> 
> On 11 May 2016 at 19:12, Sam McKelvie <sammck@gmail.com> wrote:
>> I am having this same problem. Looking at the configure script
>> it looks like it prefers to use:
>> 
>>   pkg-config sdl —static
>> 
>> to get the static linker flags, rather than:
>> 
>>  sdl-config —static-libs
> 
> Are you trying to statically compile to get a linux-user
> binary, or a system-emulation binary? For the former we
> shouldn't be linking in SDL anyway, and statically compiling
> the latter isn't really supported in my view. (Maybe we
> should make configure explicitly reject it. It has a tendency
> to break because distros don't check the static-compilation
> version of their pkg-config configuration files.)
> 
>> The former returns an empty string; the latter returns the correct
>> library list. If it had used the latter it would work properly.
>> There is a note in the configure effect suggesting that pig-config
>> is preferred, but I’m not sure why that is…
> 
> pkg-config plays better with cross compilation: you have one
> your-architecture-pkg-config which knows about the config files
> for that architecture for all libraries. Having a different
> config script for each library makes it a huge pain to try
> to swap in the right one for each architecture.
> 
> (If the two give different answers this is a distro bug.)
> 
> thanks
> -- PMM

  reply	other threads:[~2016-05-11 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 18:12 [Qemu-devel] Statically Compiling including SDL Sam McKelvie
2016-05-11 18:30 ` Peter Maydell
2016-05-11 20:39   ` Sam McKelvie [this message]
2016-05-11 22:42     ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2015-10-20  6:59 sai pavan
2015-10-20  8:35 ` Peter Maydell
2015-10-20 17:50   ` sai pavan
2015-10-20 18:22     ` Peter Maydell
2015-10-21 10:04       ` sai pavan
2015-10-21 12:18         ` Peter Maydell

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=C9CBEDB5-A704-4108-A36F-A6ED32CA8C9C@gmail.com \
    --to=sammck@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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).