All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: Internecto List Subscriber <lists@internecto.net>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Mark van Dijk <lists+xen@internecto.net>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: xen 4.2.0-rc3-pre: building failure on alpine linux / uclibc
Date: Tue, 14 Aug 2012 11:36:19 +0100	[thread overview]
Message-ID: <502A2A23.4050205@citrix.com> (raw)
In-Reply-To: <20120810163722.2feaadad@internecto.net>

Internecto List Subscriber wrote:
> On Fri, 10 Aug 2012 13:16:12 +0100
> Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> 
>> On Fri, 10 Aug 2012, Mark van Dijk wrote:
>>>> This is upstream QEMU that is breaking, not qemu-xen-traditional
>>>> (see the code path: qemu-xen-dir-remote instead of
>>>> qemu-xen-traditional-dir-remote).
>>> Ah, I didn't know, it's a little bit confusing. Would you like me to
>>> submit a bug report with them?
>>>
>>>> Moreover it is breaking compiling qemu-nbd that we aren't
>>>> currently using. I would try out the following change to the
>>>> configure script: (..snip..)
>>> Yes, that works, thanks! But it gives a new error which I couldn't
>>> solve yet:
>>>
>>> ---
>>> LINK  qemu-nbd
>>>
>>> cutils.o: In function `strtosz_suffix_unit':
>>>
>>> tools/qemu-xen-dir/cutils.c:354: undefined reference to
>>> `__isnan'
>>>
>>> tools/qemu-xen-dir/cutils.c:357: undefined reference to `modf'
>>> collect2: ld returned 1 exit status
>>> ---
>>>
>>> Any idea there?
>> It is another "-lm" missing somewhere.
> 
> Ok, well I'll leave that to the people who can actually make a healthy
> patch out of this.
> 
>>
>>> Also -- If we're not using qemu-nbd then could you suggest a
>>> workaround please? I'd prefer something that can be patched or
>>> issued before I run the make process. (I run the make process
>>> twice now - if the first run fails, patch, then run again and if it
>>> fails again error out)
>> You can disable qemu-nbd altogether with the following patch:
>> (..snip..)
> 
> While I couldn't find the proper configure script for this (I even
> grepped for stuff like 'virtfs=no' but got nothing), it was a good
> starting point. So thanks for pointing me in the right direction :)
> 
> For now building unstable on Alpine Linux works with the following
> patch:
> 
> http://pastebin.com/QU8XuM0a

Natanael Copa sent a patch to Qemu-devel some months ago to fix the
build of Qemu on uClibc, but it seems like it was ignored:

http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg02388.html

Could you try if that still applies and fixes your problems?

Roger.

  reply	other threads:[~2012-08-14 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  9:54 xen 4.2.0-rc3-pre: building failure on alpine linux / uclibc Mark van Dijk
2012-08-10 10:17 ` Stefano Stabellini
2012-08-10 12:06   ` Mark van Dijk
2012-08-10 12:16     ` Stefano Stabellini
2012-08-10 14:37       ` Internecto List Subscriber
2012-08-14 10:36         ` Roger Pau Monne [this message]
2012-08-15 20:47           ` Mark van Dijk
2012-08-16  9:56           ` Mark van Dijk

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=502A2A23.4050205@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=lists+xen@internecto.net \
    --cc=lists@internecto.net \
    --cc=xen-devel@lists.xen.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.