From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] --with-abi=<empty> ... during gcc build
Date: Sat, 29 Sep 2007 20:28:57 +0200 [thread overview]
Message-ID: <20070929182857.GS20951@aon.at> (raw)
In-Reply-To: <1191087530.5322.275.camel@elrond.atmel.sweden>
On Sat, Sep 29, 2007 at 07:38:50PM +0200, Ulf Samuelsson wrote:
>gcc configure is passed $(GCC_WITH_ABI)
>which is defined as:
>toolchain/gcc/Makefile.in:GCC_WITH_ABI:=--with-abi=$(BR2_GCC_TARGET_ABI)
Well, if it is empty it will not be set, so there is something wrong at
your end, really.
ifneq ($(strip $(subst ",,$(BR2_GCC_TARGET_ABI))),)
# ")))
GCC_WITH_ABI:=--with-abi=$(BR2_GCC_TARGET_ABI)
endif
>
>target/Config.in.arch defines BR2_GCC_TARGET_ABI
>config BR2_GCC_TARGET_ABI
> string
> default apcs-gnu if BR2_arm_dunno
> default aapcs-linux if BR2_arm_dunno
> default iwmmxt if BR2_iwmmxt
> default 32 if BR2_mipsel && BR2_OABI
> default n32 if BR2_mipsel && BR2_EABI
> default o64 if BR2_mips && BR2_OABI
> default 64 if BR2_mips && BR2_ABI64
> default eabi if BR2_mips && BR2_EABI
> default mmixware if BR2_mmix && BR2_ABI_native
> default gnu if BR2_mmix && !BR2_ABI_native
> default altivec if BR2_powerpc && BR2_ABI_altivec
>
>
>but there is no definition of BR2_OABI or BR2_EABI.
>
>Suggest the following patch
Heh. I'm extending the ABI selection for MIPS as we speak. I'll
take care of this.
next prev parent reply other threads:[~2007-09-29 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 17:38 [Buildroot] --with-abi=<empty> ... during gcc build Ulf Samuelsson
2007-09-29 18:28 ` Bernhard Fischer [this message]
2007-09-29 20:32 ` Ulf Samuelsson
2007-09-29 20:49 ` Bernhard Fischer
2007-09-29 22:12 ` Bernhard Fischer
2007-09-30 15:43 ` Ulf Samuelsson
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=20070929182857.GS20951@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox