From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: binutils fails for AVR32
Date: Mon, 21 Jul 2008 00:57:48 +0200 [thread overview]
Message-ID: <4883C2EC.90405@atmel.com> (raw)
In-Reply-To: <4883BCB1.7020102@atmel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ulf Samuelsson skrev:
|
| I managed to complete the AT91SAM9263 build, but
| now I am caught in the configure hell when trying the AVR32.
|
|
| I first got stuck in the binutils build since CC is defined as
| "'CC=ccache" in the binutils Makefile, and this should be
| "'CC=ccache gcc'"
|
| (<OpenEmbedded>/build-avr32/tmp/work/avr32-angstrom-linux-uclibc/ \
| binutils-cross-2.17-r6/binutils-2.17/ \
| build.i686-linux.avr32-angstrom-linux-uclibc/Makefile)
|
| The failure means that the initial quote character is dangling free.
|
| I tried to check binutils "configure" where this is defined
| but came to the conclusion that this was part of "$ac_arg"
| and have not managed to dig any further.
|
|
| Managed to fix that by patching binutils-avr32.inc
| Added:
|
| (cd ${B} && sed -i -e "s,'CC=ccache,'CC=ccache gcc'," Makefile)
|
| to "do_avr32_configure_bfd" but then when making "intl", there
| is a complaint that both the build and host is i686-linux.
|
| | 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.
|
Actually this refers to "./intl/configure".
BR
Ulf
| 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
|
| host_alias etc. should not be generated in the first place for
| binutils-2.17...
|
| Anyone got the AVR32 toolchain to build properly using a recent version?
|
| BR
| Ulf Samuelsson
|
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIg8LsAyRRH5cXxqwRAp84AJ9vlNOBezsHBIskXGF61ox9ECCqIQCfdfbU
Jfb36wi+w8ZGRfojXZUvzCY=
=q39W
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-07-20 23:03 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 [this message]
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
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=4883C2EC.90405@atmel.com \
--to=ulf.samuelsson@atmel.com \
--cc=openembedded-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.