public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Zhenqiang Chen <zhenqiang.chen@linaro.org>
To: crossgcc@sourceware.org
Subject: libstdc++ configure fail due to -EL option
Date: Wed, 18 Jan 2012 05:36:00 -0000	[thread overview]
Message-ID: <CACgzC7CZ_Ejrr_trorc04VfFX1qRBnp92C0=Yx3KvbvDHmzHrA@mail.gmail.com> (raw)

Hi all,

I try to build gcc trunk from crosstool-ng for arm-linux-gnueabi. But
xgcc reports error when configuring libstdc++ due to "-EL" option.

  xgcc: error: unrecognized command line option '-EL'

"-EL" is added to CT_ARCH_ENDIAN_LDFLAG since my .config uses little
endian. CT_ARCH_ENDIAN_LDFLAG is part of CT_ARCH_TARGET_LDFLAGS, which
is part of CT_TARGET_LDFLAGS.
In ./build/cc/gcc.sh:    LDFLAGS_FOR_TARGET="${CT_TARGET_LDFLAGS}.
Then, at the end "-EL" is used to compile libstdc++.

The build passes when I remove the "-EL".

Is it a bug? Which gcc supports -EL/-EB option?

Thanks!
-Zhenqiang

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-01-18  5:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  5:36 Zhenqiang Chen [this message]
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
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='CACgzC7CZ_Ejrr_trorc04VfFX1qRBnp92C0=Yx3KvbvDHmzHrA@mail.gmail.com' \
    --to=zhenqiang.chen@linaro.org \
    --cc=crossgcc@sourceware.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).