Date: Sat, 14 Jun 2014 01:17:47 +0200 From: Rolf Nielsen <rmg1970swe@gmail.com> To: Yuri <yuri@rawbw.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Build of FreeBSD-10 fails on 9 with unknown target CPU Message-ID: <539B869B.7050107@gmail.com> In-Reply-To: <539B8061.1080104@rawbw.com> References: <539AC3A7.4040309@rawbw.com> <539B2041.7000202@gmail.com> <alpine.BSF.2.00.1406131118180.46469@wonkity.com> <539B4064.1010108@rawbw.com> <539B4B04.904@gmail.com> <539B6570.5080209@rawbw.com> <539B7A27.9010106@gmail.com> <539B8061.1080104@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-14 00:51, Yuri wrote: > On 06/13/2014 15:24, Rolf Nielsen wrote: >> You never answered my questions though: Do you set some variables >> on the commandline as well, that might confuse the compiler? And >> by llvm build, do you mean when building llvm or do you mean that >> you use llvm/clang to perform the build? > > I don't set any command line variables, except NOCLEAN=YES By llvm > build I mean the section of buildworld which builds llvm. > > One thing that is special is that I do this in chroot environment > on the disk that is a bootable FreeBSD 9 root image. But this > shouldn't change anything. > > Yuri It shouldn't, especially not the CPUTYPE setting. Though in the past I've had problems building ports in chroot environments. Those problems have not been with the CPUTYPE setting, and I doubt that the chroot is the cause of your troubles, unless the chroot'ed environment is incomplete. What does it contain before you initiate the build process? Did you simply copy your running environment to a new directory and chroot into it, or did you do something more or even something less? I'm wondering where the "unknown CPU target 'amd64'" comes from. amd64 is not a valid setting for CPUTYPE, however, it is a valid setting for MACHINE_CPUARCH. Rolf P.S. I'm starting to run out of ideas, since I'm not a system hacker, and I don't really have the in-depth knowledge about the build system to go much further than this, so unless the problem is resolved, someone else will probably have to take it from here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTm4aaAAoJEB1OKfQ0M8TgazkP/ifwhguY5zwZ/FseDPbIS46a kVpPKprDi/QXMFs8glQaoDF+kXHw+aHHc8CVrksuxsbCfzUH+AF7LgsNaBWJIUEM +OWxPAWtv3CDfmA5IozuGJ7846wwCC0CmYPmpoMELbJHiXSAno/3aljTNymUWZvc xfxSLyaWT+mPnYn+Y1npkTHpZEFkg3YoKBB2Xr75TCt3oGdELdCSrhU5L8wkqHao YUyivCKmi95oAdJKKermh1vz0y5HgReE2Pvom2w6l3RZXXYJZpd3sjo8Y+T2XBBJ PUss/X8z0AIOn2AvRdpQkuvvuuG6IJmtBH0d9A6wG5c2SfVOtyCeWOTQGEQxUD1W tIGmyNpD3IO+UsqsY3ENUqcyMDY/4jyrV0JRI2eAxx8rIzlFvVDEItOCpcb3dITy auHdUWI+CGE1k+57mqFDclCI/eePQ1fUSvyPr9Fb2u6PTpAgrQjzTGICdezuheUZ R6FPc8+YthVzCINqOBz0CMK7Z41BSoVza42R5Nmw48RnPuizkPicGgC+WaVX6fQd 8cOca39FwfF+/zmo7X4AAg3fGgf8/Q3Y4a8BMpITMN+DbcaoJ+nPEWv7bGCgdcz4 Z0BlThS5yZLi31Jyz2gT65SQiFlyfcVbru2Y/5QIeks5XxbFSy60LOPaOZTHULXQ RII+IOE0akqyDWDxnWfE =eMYt -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539B869B.7050107>