qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Call for build instructions for FreeBSD and MacOSX
Date: Tue, 22 Mar 2016 09:18:53 +0000	[thread overview]
Message-ID: <87lh5aswea.fsf@linaro.org> (raw)

Hi,

I was looking at fixing a FreeBSD compile failure yesterday and I spent
a lot of time trying to figure out building on a system that I'm not
very familiar with. Today I'm having a quick look at extending the
Travis build to MacOSX.

In both cases I'm not getting very far and I notice we only really have
decent build instructions on the wiki for Linux and Win32:

  http://wiki.qemu.org/Hosts/Linux
  http://wiki.qemu.org/Hosts/W32

Could I implore the greater community to think about putting up some
simple instructions for people that are not familiar with these systems.
It will help *you* in the long run ;-)

FWIW on FreeBSD I ended up:
  * running make on the /usr/ports qemu to bring in dependencies
  * ./configure --disable-nettle (the script seems to miss this)
  * use gmake

I'm not sure if this is the right way but I did manage to reproduce the
failure that had been reported.

On MacOSX I could really do with knowing:
  * What Xcode/compiler should work
  * How are dependencies installed? (brew?)
  * Any special configure options needed?

Thanks in advance,

--
Alex Bennée

             reply	other threads:[~2016-03-22  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22  9:18 Alex Bennée [this message]
2016-03-22 10:59 ` [Qemu-devel] Call for build instructions for FreeBSD and MacOSX Peter Maydell
2016-03-22 11:37   ` Alex Bennée
2016-03-22 12:23     ` Peter Maydell
2016-03-22 12:50 ` Liviu Ionescu

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=87lh5aswea.fsf@linaro.org \
    --to=alex.bennee@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).