From: Blue Swirl <blauwirbel@gmail.com>
To: Seth G <seth.goldberg@sun.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on Solaris
Date: Sat, 6 Mar 2010 09:11:08 +0200 [thread overview]
Message-ID: <f43fc5581003052311h1529a374tc60217494b729eb0@mail.gmail.com> (raw)
In-Reply-To: <loom.20100304T032010-437@post.gmane.org>
On 3/4/10, Seth G <seth.goldberg@sun.com> wrote:
> Hi,
>
> I just sent a fair amount of time trying to figure out problems
> with the qemu build and resulting binary. The first problem (which
> is no longer a problem due to the shell OpenSolaris uses) was that
> `sh' was used in rules.mak to perform commands -- I had a /bin/sh
> that was not bash-compatible. That's a minor problem. The
Please report the errors so that we can fix the bashisms.
> more-serious problem was that once qemu was built, it would die almost
> immediately, complaining about smbus-eeprom not being an I2C device.
> That problem appears to be due to an issue with gcc's use of the
> Solaris native linker (/usr/ccs/bin/ld) -- the linker is not including
> all .o's in the .a's, even though the --whole-archive switch was passed
> to it. The linker team is looking into that problem right now, but in
> the meantime, manually performing the link step by specifying all the
> required .o's yields a usable qemu executable.
--whole-archive is no longer used since
0e8c9214ba1d4128cf92442cd343bc3733478261.
next prev parent reply other threads:[~2010-03-06 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 2:24 [Qemu-devel] qemu on Solaris Seth G
2010-03-04 6:22 ` Jonathan Kalbfeld
2010-03-04 6:39 ` Seth Goldberg
2010-03-06 7:11 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-12 15:40 [Qemu-devel] QEMU " Michele Denber
2018-08-13 8:34 ` Daniel P. Berrangé
2018-08-13 10:08 ` Peter Tribble
2018-08-13 10:20 ` Peter Maydell
2018-08-13 19:23 ` Michele Denber
2018-08-13 19:13 ` Michele Denber
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=f43fc5581003052311h1529a374tc60217494b729eb0@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=seth.goldberg@sun.com \
/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).