From: Blue Swirl <blauwirbel@gmail.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT 3f600fa] Revert "This files are compiled in libqemu.a now"
Date: Sun, 27 Sep 2009 16:37:24 +0300 [thread overview]
Message-ID: <f43fc5580909270637h34abd1b6j8490bdd70ccfb3ac@mail.gmail.com> (raw)
In-Reply-To: <20090926084910.GF6040@hall.aurel32.net>
On Sat, Sep 26, 2009 at 11:49 AM, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Sat, Sep 26, 2009 at 11:22:31AM +0300, Blue Swirl wrote:
>> On Sat, Sep 26, 2009 at 10:53 AM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>> > On Sat, Sep 26, 2009 at 09:25:29AM +0200, Aurelien Jarno wrote:
>> >> On Sat, Sep 26, 2009 at 09:44:39AM +0300, Blue Swirl wrote:
>> >> > On Fri, Sep 25, 2009 at 11:23 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>> >> > > On Fri, Sep 25, 2009 at 07:24:37PM -0000, Anthony Liguori wrote:
>> >> > >> From: Blue Swirl <blauwirbel@gmail.com>
>> >> > >>
>> >> > >> This reverts commit fe6549dfd76c278dbcd788b3c15c5e6e5ed32190.
>> >> > >>
>> >> > >> tcg-runtime and host-utils are needed on 32 bit host and they are not part
>> >> > >> of libqemu.a.
>> >> > >>
>> >> > >> Thanks to Stefan Weil for reporting.
>> >> > >>
>> >> > >
>> >> > > So what is the correct fix to the original problem? All the user-linux
>> >> > > targets are failing to build following commits
>> >> > > 96e132e24ee5a693069e83b6a981693588b088c1 and
>> >> > > c2b023b62707f5dc73497dc03f3764f145a29785:
>> >> > >
>> >> > > $ LC_ALL=C make
>> >> > > LINK i386-linux-user/qemu-i386
>> >> > > gcc: tcg-runtime.o: No such file or directory
>> >> > > gcc: host-utils.o: No such file or directory
>> >> > > make[1]: *** [qemu-i386] Error 1
>> >> > > make: *** [subdir-i386-linux-user] Error 2
>> >> >
>> >> > I can't reproduce the problem (i386 log below). Did you run make clean?
>> >> >
>> >>
>> >> Yes 'make clean' or even 'git clean -fdx' doesn't change anything, the
>> >> problem is still there.
>> >>
>> >
>> > OTOH, using configure --disable-system workarounds the problem.
>>
>> I've tried the following cases (both x86_64 + i386 host, x86_64 + i386 targets):
>> * system targets before user targets
>> * user targets before system targets
>> * just user targets
>>
>
> Some people tried to reproduce the problem on IRC, and it seems the
> conditions are:
> - use in-tree building
> - build user targets after system targets
Okay, now I can reproduce this. I try to avoid in-tree building if possible.
Perhaps there should be a -user symlink hack similar to cutils.c and
cache-utils.c. It's getting a bit ugly, though.
next prev parent reply other threads:[~2009-09-27 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909251923.n8PJNriE004578@d03av01.boulder.ibm.com>
2009-09-25 20:23 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 3f600fa] Revert "This files are compiled in libqemu.a now" Aurelien Jarno
2009-09-26 6:44 ` Blue Swirl
2009-09-26 7:25 ` Aurelien Jarno
2009-09-26 7:53 ` Aurelien Jarno
2009-09-26 8:22 ` Blue Swirl
2009-09-26 8:49 ` Aurelien Jarno
2009-09-27 13:37 ` Blue Swirl [this message]
2009-09-26 8:23 ` Aurelien Jarno
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=f43fc5580909270637h34abd1b6j8490bdd70ccfb3ac@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aurelien@aurel32.net \
--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).