Re: [Qemu-devel] Qemu 1.7.1 - configure.log contains fatal errors

[Peter Maydell]

On 14 April 2014 21:06, New B <address@hidden> wrote:
> Hi,
>
>
> Am I sending to the right forum/list?
>
> If not, I would appreciate if someone points me to the right one.

No; you want address@hidden (cc'd).

> I am new to qemu and have a few questions.
>
> Build Env Configuration:
> mac os x machine running 10.9.2 (latest Mavericks update)
> all the relevant and appropriate port/brew package installs
> Xcode 5.1.1 (latest released Xcode update) toolchain
> qemu off of tag 1.7.1 stable
>
> Build Results:
> Functional qemu executable (qemu-system-arm) that can load a linux kernel
> and rootfs
>
> Question 1- Machine configuration:
> a- Which file controls the configuration of hw devices for a machine?  For
> example, if I wanted to exclude bluetooth, would I do that in
> config-devices.mak, or in qemu/config-all-devices.mak, or
> qemu/default-configs/<cpu>-softmmu.mak ?

It's all hardcoded at the moment; you can't configure devices in and
out like that.

> b- What is arm-linux-user?

It's for running a single Linux ARM program under some other Linux
architecture. if you're on MacOSX you can ignore it (in fact we
will refuse to build it).

> Question 2- how come the binary completes in spite of following errors:
> ===>  I am positive that  a project in XCode IDE will fail to build the
> source base as it currently exists and with the same existing set of
> compiler options and defined macros.  Any pointers would be greatly
> appreciated!  <===

Building in XCode isn't a supported approach -- maybe XCode
can handle doing configure and make, or maybe not.

> a- config.log contains many compiler errors about undefined macros
> (__linux__, __OpenBSD__, _WIN32, __sun__, __HAIKU__)

That's expected. We run configure tests to see what the system
looks like, and behave accordingly depending on whether they
succeed or fail. Errors in config.log are totally normal. You only
need to worry if the actual compilation of QEMU itself fails (which
it sounds like it hasn't).

thanks
-- PMM