From owner-freebsd-arm@freebsd.org Sat Oct 14 01:07:07 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7D88E32202 for ; Sat, 14 Oct 2017 01:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 816958009E for ; Sat, 14 Oct 2017 01:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9E17ETu075402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 18:07:15 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9E17DDt075401; Fri, 13 Oct 2017 18:07:13 -0700 (PDT) (envelope-from fbsd) Date: Fri, 13 Oct 2017 18:07:13 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171014010713.GA75288@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 01:07:07 -0000 Seems it would have been better to replace BUILD_ARCH!= uname -p with BUILD_ARCH!= echo armv7 for present purposes. I'll stop the buildworld in progress and try it. Thank you! bob prohaska On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > > > It turns out that simply commenting out lines 447-452 in > > /usr/src/Makefile.inc1 allows buildworld to run, even with > > no /etc/make.conf in place. > > For reference: > > 447 .if make(buildworld) > 448 BUILD_ARCH!= uname -p > 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} > 450 .error To cross-build, set TARGET_ARCH. > 451 .endif > 452 .endif > > (I suggest that the .error message include the > MACHINE_ARCH text and the BUILD_ARCH text, probably > with ""s around each so that empty is easy to see.) > > > I've had problems with Makefiles using != and uname > ending up with the MACRO assigned being an empty string > despite a command-line uname returning the expected > text. > > For example I've applied the below local work arounds > to my /usr/ports/Mk/bsd.port.mk copy as part of setting > up to do amd64 -> aarch64 or amd64 -> armv6 cross > builds of ports via poudriere (I've not updated to a > armv7-targeting vintage sources yet): > > > # Get the operating system type > .if !defined(OPSYS) > -OPSYS!= ${UNAME} -s > +OPSYS!= echo FreeBSD > .endif > _EXPORTED_VARS+= OPSYS > > .if !defined(_OSRELEASE) > -_OSRELEASE!= ${UNAME} -r > +_OSRELEASE!= echo 12.0-CURRENT > .endif > _EXPORTED_VARS+= _OSRELEASE > > > I was specifically ending up with _OSRELEASE > being empty as seen in poudriere prior to the > workaround and that was messing up poudriere > such that it stopped with an associated > message. > > > === > Mark Millard > markmi at dsl-only.net >