qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Problems compiling HEAD on Mac OS X 10.9.2


From: Christian Mahnke
Subject: Re: [Qemu-devel] Problems compiling HEAD on Mac OS X 10.9.2
Date: Thu, 13 Mar 2014 19:34:42 +0100

Hi Peter,
it' probably a problem with the configure script, clang raised the same error:
Call to configure:
./configure  --prefix=/opt/qemu-sparc --cc=cc --target-list=sparc-softmmu,sparc64-softmmu


V=1 gmake gives

c++ -m64 -DOS_OBJECT_USE_OBJC=0 -arch x86_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common  -Wno-string-plus-int -Wno-initializer-overrides -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-definition -Wtype-limits -fstack-protector-all -I/opt/local/include -I/opt/local/include/p11-kit-1 -I/opt/local/include   -I/opt/local/include/libpng16  -I/opt/local/include/libusb-1.0  -I/opt/local/include/pixman-1  -I/Users/cmahnke/fun/qemu/dtc/libfdt -I/Users/cmahnke/fun/qemu/tests -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include  -g  -m64 -framework CoreFoundation -framework IOKit -arch x86_64 -g  -o qemu-img aio-posix.o async.o block.o block/blkdebug.o block/blkverify.o block/bochs.o block/cloop.o block/cow.o block/curl.o block/dmg.o block/nbd-client.o block/nbd.o block/parallels.o block/qapi.o block/qcow.o block/qcow2-cache.o block/qcow2-cluster.o block/qcow2-refcount.o block/qcow2-snapshot.o block/qcow2.o block/qed-check.o block/qed-cluster.o block/qed-gencb.o block/qed-l2-cache.o block/qed-table.o block/qed.o block/raw-posix.o block/raw_bsd.o block/sheepdog.o block/snapshot.o block/ssh.o block/vdi.o block/vhdx-endian.o block/vhdx-log.o block/vhdx.o block/vmdk.o block/vpc.o block/vvfat.o blockjob.o coroutine-sigaltstack.o iohandler.o main-loop.o nbd.o qapi-types.o qapi-visit.o qemu-coroutine-io.o qemu-coroutine-lock.o qemu-coroutine-sleep.o qemu-coroutine.o qemu-img.o qemu-io-cmds.o qemu-timer.o thread-pool.o libqemuutil.a libqemustub.a  -L/opt/local/lib -Wl,-headerpad_max_install_names -arch -lcurl -lssh2 -lz x86_64 -L/opt/local/lib -lgthread-2.0 -lglib-2.0 -lintl   -lz -lz
clang: error: no such file or directory: 'x86_64'
clang: error: invalid arch name '-arch -lcurl'

There are no spaces in the directory name.

There is a patch for Mac Ports which looks to me if it tries to address a similar issue, but applying thin manually doesn't work.

http://svn.macports.org/repository/macports/trunk/dports/emulators/qemu/files/patch-configure.diff

Thanks again,

Christian


On Thu, Mar 13, 2014 at 7:05 PM, Peter Maydell <address@hidden> wrote:
On 13 March 2014 17:45, Christian Mahnke <address@hidden> wrote:
> Hi list,
> I'm trying to compile the the current HEAD of the Git repository on Mac OS X
> 10.9.2 using apple-gcc42 from Mac Ports
>
> I've got the following error:
>   LINK  qemu-nbd
> i686-apple-darwin13-g++-apple-4.2.1: x86_64: No such file or directory
> c++-apple-4.2: Invalid arch name : -lcurl
>
>
> To me it seem the compiler got the options in the wrong order. Has anyone a
> hint how this can be fixed?
> Should I use a different compiler? As far as I have tested clang also
> doesn't work.

I don't have a 10.9.x system, only 10.8.x, but on that clang
builds work fine. Can you:

1. tell us what commands you used to configure and make?
2. pass "V=1" to make (which will cause it to print the
full command lines it runs) and tell us what the link
command that produced this error was?
3. tell us whether you're trying to do a build from within
a directory with a space in the name...

(For MacOSX builds these days we recommend using clang
as supplied by Apple; it used to be necessary to build
with gcc but it is not any more, and Mac gcc versions
tend to be ancient. However that doesn't look like the
problem to me.)

thanks
-- PMM


reply via email to

[Prev in Thread] Current Thread [Next in Thread]