Re: [PATCH 3/7] conf/machine/include: Cleanup MIPS tunings to match README

From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/7] conf/machine/include: Cleanup MIPS tunings to match README
Date: Fri, 6 Apr 2012 19:10:04 -0500	[thread overview]
Message-ID: <4F7F85DC.2000301@windriver.com> (raw)
In-Reply-To: <CAMKF1srkXSBHFtO__F9m9TQ=dJzfn+7kfmXoK4=tWknEdc80eg@mail.gmail.com>

Just ran a local build with the qemumips machine, this is a standard mips32 target.

 From the configure line for eglibc:

/msp-lpggp1/mhatle/git/oe-core/build-mips32/tmp-eglibc/work/mips32-oe-linux/eglibc-2.13-r23+svnr15508/eglibc-2_13/libc/configure 
--build=x86_64-linux --host=mips-oe-linux --target=mips-oe-linux --prefix=/usr 
--exec_prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
--libexecdir=/usr/libexec --datadir=/usr/share --sysconfdir=/etc 
--sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib 
--includedir=/usr/include --oldincludedir=/usr/include --infodir=/usr/share/info 
--mandir=/usr/share/man --disable-silent-rules --disable-dependency-tracking 
--with-libtool-sysroot=/msp-lpggp1/mhatle/git/oe-core/build-mips32/tmp-eglibc/sysroots/qemumips 
--enable-kernel=2.6.16 --without-cvs --disable-profile --disable-debug 
--without-gd --enable-clocale=gnu --enable-add-ons=ports,nptl,libidn,ports 
--with-headers=/msp-lpggp1/mhatle/git/oe-core/build-mips32/tmp-eglibc/sysroots/qemumips/usr/include 
--without-selinux

The system is correctly setting the target to "mips-oe-linux".

I checked and bash is the same way.

So the canonical arch is correct, the mips32 is only the packaging arch.  It was 
always intended that the packaging arch be used in full on MIPS.  (This will 
allow us to specify mips32r2, mipsiii, mipsiv, etc as necessary if we expand the 
mips tunings.)

So right now, I don't see any failure conditions with an oe-core build.  (This 
is oe-core as of earlier today.)

--Mark

On 4/6/12 4:30 PM, Khem Raj wrote:
> On Fri, Apr 6, 2012 at 10:33 AM, Mark Hatle<mark.hatle@windriver.com>  wrote:
>> On 4/4/12 11:17 PM, Khem Raj wrote:
>>>
>>> On Wed, Apr 4, 2012 at 3:10 PM, Andreas Oberritter<obi@opendreambox.org>
>>>   wrote:
>>>>
>>>>
>>>> What was mipsel-oe-linux before now became mips32el-oe-linux, i.e.
>>>> tmp/work/mipsel-oe-linux now is tmp/work/mips32el-oe-linux. I'm not sure
>>>> what else broke.
>>>>
>>>> Was this intentional?
>>>
>>>
>>> I dont think so. mips-*-* in general indicates 32bit BE mips and
>>> mipsel-*-* indicates
>>> 32bit LE mips so devicing mips32 and mips32el may be more explicit but
>>> is not widely
>>> used norm
>>
>>
>> If that has changed it was certainly not intentional.  As Khem said the
>> expected GNU canonical archs are:
>>
>> mips-*-*
>> mipsel-*-*
>> mips64-*-*
>> mips64el-*-*
>>
>> mips32 should work, but it was not expected to have changed.
>>
>> Looking through, the GNU canonical arch should only match the above.  The
>> namings in the tmp/work directory are strictly following the -package arch-
>> namings, which don't affect system configuration.
>>
>> I checked the logs from my test builds, and the mips32* reused the mips*
>> builds because the canonical arch of the configuration and such were the
>> same.
>>
>> (Looked at config.log in a couple of packages...)  if you see mips32-* in
>> the config.log, let me know.
>
> see angstrom buildhistory its all filled with changes from mips ->  mips32
> its unwanted.
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core