Date: Wed, 16 Mar 2016 00:07:50 +0100 From: "Ronald Klop" <ronald-lists@klop.ws> To: freebsd-arm@freebsd.org Subject: Re: libunwind does not compile Message-ID: <op.yed2jcc1kndu52@53555a16.cm-6-6b.dynamic.ziggo.nl> In-Reply-To: <1458054610.68920.17.camel@freebsd.org> References: <op.yebzffztkndu52@53555a16.cm-6-6b.dynamic.ziggo.nl> <1458054610.68920.17.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Mar 2016 16:10:10 +0100, Ian Lepore <ian@freebsd.org> wrote: > On Mon, 2016-03-14 at 21:05 +0100, Ronald Klop wrote: >> Hello, >> >> I'm cross compiling for Sheevaplug on a recent amd64/11-CURRENT with >> clang >> 3.8.0. >> uname: FreeBSD sjakie.klop.ws 11.0-CURRENT FreeBSD 11.0-CURRENT #8 >> r296724M: Sun Mar 13 16:03:31 CET 2016 >> root@sjakie.klop.ws:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 >> >> Using these settings: >> export TARGET_ARCH=arm >> export MAKEOBJDIRPREFIX=/usr/obj-arm >> export KERNCONF=SHEEVAPLUG >> export WITH_NAND=yes >> export WITH_ARM_EABI=yes >> export WITH_GCC=yes >> export WITH_GNUCXX=yes >> export WITHOUT_CLANG_IS_CC=yes >> export NO_CLEAN=yes >> export DESTDIR=/mnt/usbdisk >> >> I get the error below. Is this known/expected? What can I do to fix >> it? I >> build gcc because clang 3.7 did not work on arm (although it could >> cross-compile to arm). >> >> >> ===> gnu/lib/libgcc (obj,depend,all,install) >> (cd /usr/src-arm/gnu/lib/libgcc; make -f >> /usr/src-arm/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile >> MFILE=/usr/src-arm/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile >> GCCDIR=/usr/src-arm/gnu/lib/libgcc/../../../contrib/gcc gthr >> -default.h) >> `gthr-default.h' is up to date. >> (cd /usr/src-arm/gnu/lib/libgcc; make -f >> /usr/src-arm/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile >> MFILE=/usr/src-arm/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile >> GCCDIR=/usr/src-arm/gnu/lib/libgcc/../../../contrib/gcc unwind.h) >> `unwind.h' is up to date. >> cc -O -pipe -DTARGET_ARM_EABI -DIN_GCC -DIN_LIBGCC2 >> -D__GCC_FLOAT_NOT_NEEDED -DHAVE_GTHR_DEFAULT >> -I/usr/src-arm/gnu/lib/libgcc/../../../contrib/gcclibs/include >> -I/usr/src-arm/gnu/lib/libgcc/../../../contrib/gcc/config >> -I/usr/src-arm/gnu/lib/libgcc/../../../contrib/gcc -I. >> -I/usr/src-arm/gnu/lib/libgcc/../../usr.bin/cc/cc_tools >> -Dinhibit_libc >> -fno-inline -std=gnu99 -fheinous-gnu-extensions -Qunused-arguments >> -c >> /usr/src >> -arm/gnu/lib/libgcc/../../../contrib/gcc/config/arm/libunwind.S -o >> libunwind.o >> /usr/src >> -arm/gnu/lib/libgcc/../../../contrib/gcc/config/arm/libunwind.S:29:10 >> : >> fatal error: 'machine/acle-compat.h' file not found >> #include <machine/acle-compat.h> >> ^ >> 1 error generated. >> *** [libunwind.o] Error code 1 > > When I crossbuild -current for dreamplug and I want gcc instead of > clang, I use these settings: > > WITH_GCC=yes > WITH_GNUCXX=yes > WITH_GCC_BOOTSTRAP=yes > WITHOUT_CLANG=yes > WITHOUT_CLANG_IS_CC=yes > WITHOUT_CLANG_BOOTSTRAP=yes > > That said, you may also be interested to hear that clang 3.8 runs fine > on a *plug on -current. I've been using clang 3.8 (from the project > branch before the recent merge to current) and gcc on my dreamplug > within the past month. > > -- Ian > Ah, ok. I don't want to cross-build everything with gcc. I only had gcc installed as cc, because clang did not work on the arm machine. Does WITHOUT_CLANG_IS_CC does something more than 'man src.conf' mentions? I just removed WITHOUT_CLANG_IS_CC=yes and now the build continues. See what happens after a night sleep while clang compiles. :-) Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.yed2jcc1kndu52>