All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU static build
Date: Wed, 16 Jan 2008 14:20:23 +0100	[thread overview]
Message-ID: <478E0497.6060108@linux.vnet.ibm.com> (raw)
In-Reply-To: <7f7951300801160459m734eff80n32d902a0e1608872@mail.gmail.com>

Salil Bijur wrote:
> On Jan 16, 2008 5:59 PM, Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com> wrote:
>> Salil Bijur wrote:
>>> On Jan 16, 2008 4:48 PM, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
>>>> Hi
>>>>
>>>>
>>>> On Jan 16, 2008 5:20 PM, Salil Bijur <salilbijur@gmail.com> wrote:
>>>>> Hello,
>>>>>
>>>>> I've been trying to build QEMU statically by first configuring it
>>>>> using the --static option. The compiling gives me the same linker
>>>>> errors as mentioned here:
>>>>> http://www.mail-archive.com/qemu-devel@nongnu.org/msg10721.html
>>>>>
>>>>> I know this has been asked before but it hasn't been followed up. Any
>>>>> ideas on how to fix this?
>>>> What do you want to do? to debug it? if yes, maybe you just want the
>>>> unstripped binary? dig qemu-devel and qemu-forum.... or at least try
>>>> the binary in target-i386..i believe it's unstripped. Can check it
>>>> here, because my box use gcc 4.x
>>>>
>>> I'm trying to build qemu-system-arm so my configure command is
>>> "./configure --target-list=arm-softmmu --static". I need a static
>>> build to overcome dynamic library dependency issues. Doing a 'make'
>>> with the above configure command breaks. I haven't found a solution on
>>> the forums.
>>>
>>> Thanks,
>>> Salil
>> I sometimes use a static build for the same reasons on ppc.
>> I did not have the same issue but I usually set LDFLAGS="$LDFLAGS -pthread" before doing configure&make.
>> Maybe it's worth a try if this helps your linker to find the pthread functions.
>>
> 
> Thanks - I did 'export LDFLAGS="$LDFLAGS -pthread"' before configure
> and it compiles further.
> 
> But there are further linker errors with respect to libasound (for
> ALSA) and libSDL. This can be solved by adding -ldl, -lartsc, etc. for
> every dependency of these libs but would be very tedious, especially
> for libSDL. Any better solution?
> 

The question is if you really need SDL for your environment - if not you can just add "--disable-sdl" and do the same with everything else e.g. alsa that is missing but not really needed.



-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

  parent reply	other threads:[~2008-01-16 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 10:20 [Qemu-devel] QEMU static build Salil Bijur
2008-01-16 11:18 ` Mulyadi Santosa
2008-01-16 11:48   ` Salil Bijur
2008-01-16 11:59     ` Mulyadi Santosa
2008-01-16 12:29     ` Christian Ehrhardt
2008-01-16 12:59       ` Salil Bijur
2008-01-16 13:04         ` Samuel Thibault
2008-01-16 13:20         ` Christian Ehrhardt [this message]
2008-01-16 13:28           ` Salil Bijur
2008-01-16 15:45             ` Thiemo Seufer
2008-01-18  8:00               ` Salil Bijur

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=478E0497.6060108@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.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 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.