[oe] [STABLE][PATCH] mingw-binutils: update to 2.19.1

Esben Haabendal esbenhaabendal at gmail.com
Tue Apr 7 07:11:17 UTC 2009


On Tue, Apr 7, 2009 at 1:54 AM, Tom Rini <trini at kernel.crashing.org> wrote:
> On Tue, Apr 07, 2009 at 01:14:07AM +0200, Esben Haabendal wrote:
>
>> Signed-off-by: Esben Haabendal <eha at doredevelopment.dk>
>> ---
>>  .../mingw-binutils-canadian-cross_2.19.1.bb        |   11 +++++++++++
>>  recipes/binutils/mingw-binutils_2.19.1.bb          |   12 ++++++++++++
>>  2 files changed, 23 insertions(+), 0 deletions(-)
>>  create mode 100644 recipes/binutils/mingw-binutils-canadian-cross_2.19.1.bb
>>  create mode 100644 recipes/binutils/mingw-binutils_2.19.1.bb
>
> First, this isn't in .dev yet.  Second..

I know, it should apply there cleanly as well, but I need to test it...

>> diff --git a/recipes/binutils/mingw-binutils-canadian-cross_2.19.1.bb
>> b/recipes/binutils/mingw-binutils-canadian-cross_2.19.1.bb
>> new file mode 100644
>> index 0000000..27e06c6
>> --- /dev/null
>> +++ b/recipes/binutils/mingw-binutils-canadian-cross_2.19.1.bb
>> @@ -0,0 +1,11 @@
>> +require mingw-binutils_${PV}.bb
>> +require binutils-canadian-cross.inc
>> +
>> +DEFAULT_PREFERENCE_sdk-mingw32 = "1"
>> +DEFAULT_PREFERENCE_sdk-mingw64 = "1"
>
> That's meaningless atm.  Or at least it is for how I've been doing all
> of the build tests (SDK_OS=mingw32), it would be just _mingw32 (does
> mingw64 work yet?).  Finally, do we really want to make this default
> when we're still building gcc-3.4.5?  I wouldn't think so, but I assume
> this means a gcc 4 actual release is soon.

The gcc 4 relase from MinGW project seem to have been in the same
state for quite a while.
I wonder when they will change it.

Any special reason why we don't want to use a newer binutils for gcc-3.4.5?

I don't remember seeing any problems with that, but maybe I have just
been lucky on that issue :-)

The reason I pulled in this release was actually that I had a failure
with ld from the old binutils when building mingw-runtime.
So unless something points against setting 2.19.1 as default, I think we should.

> Oh, and you forgot to add in checksums :)

Ah, sorry.

/Esben


-- 
Esben Haabendal, Senior Software Consultant
DoréDevelopment ApS, Ved Stranden 1, 9560 Hadsund, DK-Denmark
Phone: +45 51 92 53 93, E-mail: eha at doredevelopment.dk
WWW: http://www.doredevelopment.dk




More information about the Openembedded-devel mailing list