Date: Sat, 14 Oct 2017 10:54:07 -0600 From: Warner Losh <imp@bsdimp.com> To: =?UTF-8?Q?Eddy_Petri=C8=99or?= <eddy.petrisor@gmail.com> Cc: Michal Meloun <mmel@freebsd.org>, freebsd-arm@freebsd.org, bob prohaska <bob@www.zefox.net> Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <CANCZdfp2khWQKLRqG0%2BQ-Z1WfwFKyq7xkrVau8scd=EPLkC0xQ@mail.gmail.com> In-Reply-To: <CAK0XTWeRbhghXotPT6jTosDGjD3TF00TsG%2Bes0AVsFuU-FyQVw@mail.gmail.com> References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <CANCZdfrKYabu1-bWxX47=Lt=33e%2BFjBXCNBNiGPE7K-83KOAHA@mail.gmail.com> <CANCZdfqHfAe24q=6n8CxsHQv24j58bQLPG3z_7vi_xpGjdQzDg@mail.gmail.com> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <F9F4D731-35CD-44E6-8419-D73CB98655E9@dsl-only.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> <CAK0XTWeRbhghXotPT6jTosDGjD3TF00TsG%2Bes0AVsFuU-FyQVw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" <eddy.petrisor@gmail.com> wr=
ote:
Pe 14 oct. 2017 7:28 AM, "Michal Meloun" <melounmichal@gmail.com> a scris:
On 14.10.2017 4:11, bob prohaska wrote:
> On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote:
>> On 2017-Oct-13, at 6:07 PM, bob prohaska <fbsd@www.zefox.net> wrote:
>>
>>> Seems it would have been better to replace
>>> BUILD_ARCH!=3D uname -p
>>> with
>>> BUILD_ARCH!=3D echo armv7
>>> for present purposes.
>>
>> Are you starting under armv6 ? armv7 ?
> I'm afraid it's a mix, due to some untimely foot-shooting.
>
> Uname - p reports armv7, but clang -v reports
> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on
LLVM 4.0.0)
> Target: armv6-unknown-freebsd12.0-gnueabihf
> Thread model: posix
> InstalledDir: /usr/bin
>
> I'll keep trying to unscramble the mess I've made until an armv7 RPI2
> snapshot is released, then start over if necessary.
>
> Thanks for reading!
>
> bob prohaska
>
Bob,
can you please try this?
setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darmv7
I have been trying recently to add support for cross building FreeBSD from
Linux and concluded that MACHINE is the system on which the build is done.
At the start of the build, yes. But we set it while doing the actual cross
build to the target.
I don't think I found BUILD* meaning yet.
That's because they are internal and should never be messed with. They are
a detail we don't commit to keeping. If they matter, we have done
something wrong.
Unfortunately I concluded the FreeBSD build system would really benefit
from a clean-up in terms of variables and documenting their use. May I
suggest creating a wiki page documenting the usage a clean up can be done?
We do document most of them in build man page. That's what should be
updated. It spells this stuff out.
Warner
Michal
>
>> BUILD_ARCH should end up matching what
>> you start under, not the end target as
>> I understand things.
>>
>> If I tried a cross build on a host
>> other than armv7 that BUILD_ARCH result
>> would be wrong. (I use amd64 for cross
>> building aarch64 and arm6 . I'm not up to
>> an armv7 capable context yet and may not
>> be for some time.)
>>
>> That change is a local workaround that is
>> specific to the environment you are using
>> for a build.
>>
>> This is like my 12.0-CURRENT change being
>> specific to my not building on 11.x or 10.x .
>> It is just a local workaround that applies
>> just to a more limited context.
>>
>> I've not figured out what is going on (how/why)
>> for the !=3D uname behavior that I observed. But
>> echoing the expected result instead did work.
>>
>> None of this is appropriate to check-in.
>>
>>> I'll stop the buildworld in progress and try it.
>>
>> Please report if echo of the host type of context
>> appears to make your local environment work vs.
>> not. If it does work then it suggests that
>> !=3D uname -p did not get the expected text for
>> some reason.
>>
>> Older material:
>>
>> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote:
>>> On 2017-Oct-13, at 10:59 AM, bob prohaska <fbsd at www.zefox.net> 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!=3D uname -p
>>> 449 .if ${MACHINE_ARCH} !=3D ${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 !=3D 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!=3D ${UNAME} -s
>>> +OPSYS!=3D echo FreeBSD
>>> .endif
>>> _EXPORTED_VARS+=3D OPSYS
>>>
>>> .if !defined(_OSRELEASE)
>>> -_OSRELEASE!=3D ${UNAME} -r
>>> +_OSRELEASE!=3D echo 12.0-CURRENT
>>> .endif
>>> _EXPORTED_VARS+=3D _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.
>>
>>
>> =3D=3D=3D
>> Mark Millard
>> markmi at dsl-only.net
>>
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
>
_______________________________________________
freebsd-arm@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
_______________________________________________
freebsd-arm@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp2khWQKLRqG0%2BQ-Z1WfwFKyq7xkrVau8scd=EPLkC0xQ>