svn commit: r266553 - head/release/scripts

[Tijl Coosemans]

On Mon, 26 May 2014 16:31:21 -0600 Warner Losh wrote:
> On May 26, 2014, at 4:18 PM, Tijl Coosemans <tijl at FreeBSD.org> wrote: 
>> On Mon, 26 May 2014 09:53:57 -0600 Warner Losh wrote:
>>> On May 26, 2014, at 8:39 AM, Nathan Whitehorn <nwhitehorn at freebsd.org> wrote:
>>>> On 05/26/14 02:35, Tijl Coosemans wrote:
>>>>> I suppose you could replace the "x86" in the pkg scheme with i386/amd64,
>>>>> but then you'd still be talking about i386:32, amd64:32 and amd64:64
>>>>> instead of x86:32, x86:x32 and x86:64.  
>>> 
>>> I suppose you could replace these by “i386”, “x32” (or “amd64x32”) and
>>> “amd64” respectively.
>> 
>> So you're on an amd64 or mips64 system (as indicated by uname) but you
>> want to use the 32-bit package if possible.  How does your script know
>> about the magic "x32", "amd64x32" or "mipsn32" strings?  Wouldn't it be
>> easier if you could just use "`uname -p`:32”?
> 
> Oh give me a break. You know it because you know you are building for
> mipsn32 because that’s what you’ve set MACHINE_ARCH or TARGET_ARCH to,

No, MACHINE_ARCH or TARGET_ARCH is "amd64" or "mips64".  You are building
the 64-bit OS and then decide separately per package whether you want the
ILP32 one or the LP64 one.