From owner-freebsd-questions@FreeBSD.ORG Fri Jun 13 23:17:52 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A673ACB for ; Fri, 13 Jun 2014 23:17:52 +0000 (UTC) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A423F20BF for ; Fri, 13 Jun 2014 23:17:51 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id 10so774237lbg.37 for ; Fri, 13 Jun 2014 16:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=h+V6xfviGaCJbM8Pe7umRq2FFJn6s4k5+EL1jBZVZ+s=; b=heMYnia2gmwK+4o2TB82FFMTLtqSK90XXu+FgmkRk0NL7lX8bozEjUOOwboM0Xj2ns 89FjZ0o5z0+1jw/htiUrxLiySIYoSloslEhCiVN5elUVGFifwPhw0IMioCkcOK7fifcd BANEWZ6WCr3AgcDklDxZnHYUFswqCkITshh8EXmuJnICsQ57DlXlHxVoKRUdTnsD+Hwx VbPoTVYQu8qYUmLfxR/sxk4tidi/dW5ahiykAb+lkSHLyf1teC+9kpvJLuVzt64PfovD g7YHKe2FymzHpr+7CUhw+b9B8AwuMJMDV2jw7kZlkItrzIjhIJA5zA51+W7u9XkZAvLR ku/g== X-Received: by 10.112.162.70 with SMTP id xy6mr3426650lbb.40.1402701468995; Fri, 13 Jun 2014 16:17:48 -0700 (PDT) Received: from lazlar.no-ip.biz (109.58.145.172.bredband.tre.se. [109.58.145.172]) by mx.google.com with ESMTPSA id o8sm1349667laj.10.2014.06.13.16.17.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 16:17:48 -0700 (PDT) Message-ID: <539B869B.7050107@gmail.com> Date: Sat, 14 Jun 2014 01:17:47 +0200 From: Rolf Nielsen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Yuri Subject: Re: Build of FreeBSD-10 fails on 9 with unknown target CPU References: <539AC3A7.4040309@rawbw.com> <539B2041.7000202@gmail.com> <539B4064.1010108@rawbw.com> <539B4B04.904@gmail.com> <539B6570.5080209@rawbw.com> <539B7A27.9010106@gmail.com> <539B8061.1080104@rawbw.com> In-Reply-To: <539B8061.1080104@rawbw.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 23:17:52 -0000 -----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-----