From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] problem with gcc and arch/tune/cpu option
Date: Thu, 25 Jan 2007 01:18:25 +0100 [thread overview]
Message-ID: <20070125001824.GH28221@aon.at> (raw)
In-Reply-To: <45B773BA.2060904@ifotec.com>
On Wed, Jan 24, 2007 at 03:56:58PM +0100, St?phane Champeau wrote:
>Hi all,
>
>I have a problem with :
>buildroot rev 17495
>ARM920T / EABI / gcc 4.2 20070117
>kernel 2.6.19.2 / binutils 2.17.50.0.9
>uclibc snapshot / busybox snapshot
>soft-float / LFS
>
>I have this error :
>Unknown CPU used in --with-cpu=arm
>make[1]: *** [configure-gcc] Erreur 1
>make[1]: quittant le r?pertoire
>?/buildroot/toolchain_build_arm_nofpu/gcc-4.2-initial ?
>make: ***
>[buildroot/toolchain_build_arm_nofpu/gcc-4.2-initial/.compiled] Erreur 2
>
>In fact gcc is configured with :
>--with-cpu=arm --with-arch=arm --with-tune=arm
>This is an error
>(http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#ARM-Options)
>
>I think a part of patch 17473 break the toolchain :
>In the file buildroot/toolchain/gcc/gcc-uclibc-3.x.mk line 384
>if I put this :
>GCC_WITH_ARCH=--with-arch=armv4t
>GCC_WITH_TUNE=--with-tune=arm920t
>GCC_WITH_CPU=--with-cpu=arm920t
>instead of :
>GCC_WITH_ARCH=--with-arch=$(BR2_ARCH)
>GCC_WITH_TUNE=--with-tune=$(BR2_ARCH)
>GCC_WITH_CPU=--with-cpu=$(BR2_ARCH)
>I can build the toolchain
We will have to cleanup the BR2_ARCH, BR2_SUBARCH/BR2_CPU selection.. hmz
Thanks for noticing. I've reverted this bit until it gets fixed for
good. Sorry for any inconvenience this may have caused.
prev parent reply other threads:[~2007-01-25 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 14:56 [Buildroot] problem with gcc and arch/tune/cpu option Stéphane Champeau
2007-01-25 0:18 ` Bernhard Fischer [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=20070125001824.GH28221@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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.