[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140813091843.GD5170@example.net>
Date: Wed, 13 Aug 2014 11:18:43 +0200
From: u-igbb@...ey.se
To: musl@...ts.openwall.com
Subject: compiling musl on x86_64 linux with ppc
Hello,
I am trying to compile musl 1.1.4 on x86_64 with ppc (latest from cvs).
Unfortunately the compilation breaks with
-----------
...
pcc -std=c99 -nostdinc -ffreestanding -fexcess-precision=standard -frounding-math -D_XOPEN_SOURCE=700 -I./arch/x86_64 -I./src/internal -I./include -Os -pipe -fomit-frame-pointer -fno-unwind-tables -fno-asynchronous-unwind-tables -Wa,--noexecstack -Werror=implicit-function-declaration -Werror=implicit-int -Werror=pointer-sign -Werror=pointer-arith -fno-stack-protector -c -o src/aio/aio_readwrite.o src/aio/aio_readwrite.c
./arch/x86_64/syscall_arch.h, line 37: warning: no register assignment (yet)
./arch/x86_64/syscall_arch.h, line 46: warning: no register assignment (yet)
./arch/x86_64/syscall_arch.h, line 47: warning: no register assignment (yet)
./arch/x86_64/syscall_arch.h, line 56: warning: no register assignment (yet)
./arch/x86_64/syscall_arch.h, line 57: warning: no register assignment (yet)
./arch/x86_64/syscall_arch.h, line 58: warning: no register assignment (yet)
src/aio/aio_readwrite.c, line 23: compiler error: unsupported xasm constraint r11
error: XXXXX/libexec/ccom terminated with status 1
make: *** [src/aio/aio_readwrite.o] Error 1
-----------
Is there any way around this, short of adding the register assignment
functionality to the compiler?
Regards,
Rune
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
