Date: Sun, 18 Oct 2015 10:48:16 -0600 From: Ian Lepore <ian@freebsd.org> To: Jukka Ukkonen <jau789@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: machine/acle-compat.h missing Message-ID: <1445186896.71631.57.camel@freebsd.org> In-Reply-To: <59E5C236-908F-4AAA-942B-7E5FE5B76C0D@gmail.com> References: <561B4A25.2030703@gmail.com> <20151012232952.GR67524@funkthat.com> <qdnhjn.nw50ar.1hge18i-qmf@smtp.gmail.com> <626A93AA-8E14-4027-8FFC-95CA2AC77193@kientzle.com> <59E5C236-908F-4AAA-942B-7E5FE5B76C0D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
We need to be very clear here that the problem is the procedure you are using to build, and not anything with the build system or the compilers. I build arm 11 images on 10-stable every day, using the documented procedures (which certainly do NOT involve overriding CC and CXX), as do many other people. The first step of a build is to use the existing system compiler to build the latest compiler, which is then used to build the rest of the source. The default clang 3.4 on 10-stable has no problem building clang 3.7 as the first step of an arm build, and that clang 3.7 is then used to compile world and kernel. More details on the build process can be found here: https://wiki.freebsd.org/FreeBSD/arm/crossbuild It's oriented towards a setup for doing freebsd development for multiple boards, but there's good general info there for anyone doing their own builds without using the crochet tool. -- Ian On Tue, 2015-10-13 at 08:32 +0300, Jukka Ukkonen wrote: > Quite recently the 11.x builds using clang 3.4.1 started giving me > trouble. > If I remember correctly, the older clang had problems with the more > recent clang source. So, after browsing the UPDATING file a little I > found > a note there explaining how the clang source in 11.x now needs at > least > clang 3.5 to compile. That is how I ended up overriding CC and CXX. > Then started the problems with acle-compat.h. > I guess the dilemma is twofold. Is this file really used at all? If > so, why > does it not appear where it is expected to be found? If not really > used, > is it included in error when I override the compiler? > > I guess the problem might not happen when compiling on the rpi2 > itself > or on another 11.x system. In fact I am going to update the source on > the rpi2 and launch a test build locally on the target later today. > The local builds on rpi2 just take some 11 hours or so. Obviously I > run > those very rarely. > > --jau > > > Sent from my iPad > > > On 13 Oct 2015, at 06:34, Tim Kientzle <tim@kientzle.com> wrote: > > > > Do you get the same problem if you do not override CC and CXX? > > > > I¢ve never needed to set those. > > > > Tim > > > > > > > On Oct 12, 2015, at 7:29 PM, jau789@gmail.com wrote: > > > > > > The build environment is amd64 running 10-stable. > > > The native cc is obviously clang 3.4.1. > > > The build target in has been rpi2. > > > To make current build possible at all CC and CXX > > > are set to clang37 and clang++37 during the make > > > run. > > > > > > --jau > > > > On 13/10/2015 2:29 John-Mark Gurney wrote: > > > > Jukka Ukkonen wrote this message on Mon, Oct 12, 2015 at 08:50 > > > > +0300: > > > > After the latest clang update in current cross-compilation for > > > > arm > > > > has been failing due to "missing" > > > > > > Do you mean armeb? or what specific arch? > > > > > > > <machine/acle-compat.h> > > > > > > > > The file is apparently present... > > > > > > > > src.head/sys/arm/include/acle-compat.h > > > > > > > > but the compiler fails to find it because for some reason it > > > > never gets copied to the path where the compiler expects to > > > > find it... > > > > > > > > /tank/fish/jau/Xcomp/src.head/gnu/lib/libgcc/../../../contrib/g > > > > cc/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 > > > > > > > > Has anyone else noticed this, or is it just me doing something > > > > odd? > > > > > > Are you using gcc, or the default of clang now? > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1445186896.71631.57.camel>