From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: binutils fails for AVR32
Date: Sat, 04 Oct 2008 10:38:03 +0200 [thread overview]
Message-ID: <48E72B6B.8090907@linuxdevelopment.de> (raw)
In-Reply-To: <gc5djj$4em$1@ger.gmane.org>
Koen Kooi wrote:
> On 03-10-2008 13:46, Robert Wörle wrote:
>>> | Configuring in ./intl
>>> | configure: warning: build_alias=i686-linux: invalid host type
>>> | configure: warning: host_alias=i686-linux: invalid host type
>>> | configure: error: can only configure for one host and one target at a
>>> time
>>> | make[1]: *** [configure-intl] Error 1
>>> | make[1]: Leaving directory
>>> `/mnt/home/ulf/OpenEmbedded/build-avr32/tmp/work/avr32-angstrom-linux-uclibc/binutils-cross-2.17-r6/binutils-2.17/build.i686-linux.avr32-angstrom-linux-uclibc'
>>>
>>>
>>> | make: *** [all] Error 2
>>> | FATAL: oe_runmake failed
>>>
>>> These problems seems to be caused by build_alias, host_alias and
>>> target_alias beeing passed to "configure", but these are only
>>> supported by binutils-2.18 and not 2.17 which is used by the AVR32.
>>>
>>> I am adding
>>> ~ (cd ${B}&& sed -i -e "s,'host_alias=i686-linux',," Makefile)
>>> ~ (cd ${B}&& sed -i -e "s,'build_alias=i686-linux',," Makefile)
>>> ~ (cd ${B}&& sed -i -e "s,'target_alias=avr32-angstrom-linux-uclibc',,"
>>> Makefile)
>>>
>>> to the do_avr32_configure_bfd
>>>
>> Did you add this as prepend to this stage ? in which bb file did you add
>> it ?
>> Did the whole toolchain work out for you now ?
>
> It seems your metadata is obsolete, avr32 builds have 'just worked' for
> a few months now thanks to several companies funding OE avr32 work.
>
> A sample of what angstrom can do now:
>
> http://www.youtube.com/watch?v=vvOyixL8BRM
>
wow thats cool !
btw .. i just managed to build avr32 again with the current meta`s by
just removing the binutils-avr32.inc !! It went on and finished
minimal-image !
And that on a x86_64 host ! What a joy
Hail you, Koen and the others .. feels like i can now relay on the oe
chain again and start building up more products on this nice cpu
Cheers Rob
>
> Koen
prev parent reply other threads:[~2008-10-04 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 22:31 binutils fails for AVR32 Ulf Samuelsson
2008-07-20 22:57 ` Ulf Samuelsson
2008-07-22 17:42 ` Leon Woestenberg
2008-08-10 13:19 ` Robert Schuster
2008-08-10 13:58 ` Koen Kooi
2008-08-10 16:37 ` Robert Schuster
2008-10-03 11:46 ` Robert Wörle
2008-10-03 15:26 ` Koen Kooi
2008-10-04 8:38 ` Robert Wörle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48E72B6B.8090907@linuxdevelopment.de \
--to=robert@linuxdevelopment.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox