From: Mike Frysinger <vapier@gentoo.org>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: crossgcc@sourceware.org,
Zhenqiang Chen <zhenqiang.chen@linaro.org>,
Khem Raj <raj.khem@gmail.com>
Subject: Re: libstdc++ configure fail due to -EL option
Date: Mon, 23 Jan 2012 22:08:00 -0000 [thread overview]
Message-ID: <201201231708.18054.vapier@gentoo.org> (raw)
In-Reply-To: <CAJ+oik0SJHfqH1AwbCQLPjtqKNLNaSrP3xpJUKVn=0oXog-d_w@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1543 bytes --]
On Monday 23 January 2012 16:08:39 Bryan Hundven wrote:
> On Wed, Jan 18, 2012 at 2:28 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Wednesday 18 January 2012 02:09:09 Zhenqiang Chen wrote:
> >> > -EL is only valid for mips gcc as far as ct-ng is concerned. It should
> >> > not be used for arm configurations since arm is little endian by
> >> > default pluis this is an invalid option you need
> >> > -mlittle-endian for arm if you really want to specify it explicitly.
> >>
> >> -EL/-EB is added in crosstool-ng automatically. Here is the code
> >> segment in scripts/functions
> >>
> >> CT_DoBuildTargetTuple() {
> >> # Set the endianness suffix, and the default endianness gcc option
> >> case "${CT_ARCH_ENDIAN}" in
> >> big)
> >> target_endian_eb=eb
> >> target_endian_el=
> >> CT_ARCH_ENDIAN_CFLAG="-mbig-endian"
> >> CT_ARCH_ENDIAN_LDFLAG="-EB"
> >> ;;
> >> little)
> >> target_endian_eb=
> >> target_endian_el=el
> >> CT_ARCH_ENDIAN_CFLAG="-mlittle-endian"
> >> CT_ARCH_ENDIAN_LDFLAG="-EL"
> >> ;;
> >> esac
> >
> > LDFLAGS should take the form as needed by the compiler driver. i.e.
> > -Wl,-EL.
>
> Well, we'd get the same error if we pass -Wl,-EL to ld, where that
> would fix it for passing to gcc.
yes, but generally speaking, you should not be invoking the linker.
everything should be going through the compiler driver.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-23 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 5:36 Zhenqiang Chen
2012-01-18 5:43 ` Bryan Hundven
2012-01-18 5:52 ` Khem Raj
2012-01-18 7:09 ` Zhenqiang Chen
2012-01-18 7:10 ` Bryan Hundven
2012-01-18 7:22 ` Khem Raj
2012-01-18 7:28 ` Bryan Hundven
2012-01-18 8:02 ` Yann E. MORIN
[not found] ` <CAJ+oik0gsKpXgzR4cOxhyujv+=H-fuFsuhRouch9T2hz73U2FA@mail.gmail.com>
2012-01-18 8:47 ` Yann E. MORIN
2012-01-18 8:52 ` Zhenqiang Chen
2012-01-18 10:28 ` Mike Frysinger
2012-01-23 21:08 ` Bryan Hundven
2012-01-23 22:08 ` Mike Frysinger [this message]
2012-01-23 22:13 ` Bryan Hundven
2012-01-23 22:37 ` Yann E. MORIN
2012-01-23 23:55 ` Mike Frysinger
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=201201231708.18054.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=raj.khem@gmail.com \
--cc=zhenqiang.chen@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).