From: Ian Lance Taylor <ian@wasabisystems.com>
To: "Arthur Yang" <arthuryang@online.cq.cn>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: arm-linux-gcc can't recognize "-mpreferred-stack-boundary"
Date: Sat, 27 Nov 2004 02:46:00 -0000 [thread overview]
Message-ID: <m3brdk3t6x.fsf@gossamer.airs.com> (raw)
In-Reply-To: <001301c4d3ab$38731130$0101a8c0@arthur>
"Arthur Yang" <arthuryang@online.cq.cn> writes:
> However when I build glibc, I found error caused by that arm-linux-gcc can't recognizing "preferred-stack-boundary=4". The output is attached at the end of the mail.
>
> So I checked like this:
> gcc -mpreferred-stack-boundary=4 tt.c
> It's OK.
> arm-linux-gcc -mpreferred-stack-boundary=4 tt.c
> it responded as below:
> cc1: error: invalid option `preferred-stack-boundary=4'
Yes. -mpreferred-stack-boundary is an i386-specific option.
This problem would seem to be in the glibc cross-build procedure. It
is using an i386-specific option for the ARM compiler. I don't know
why. It's not a compiler bug. You will have to talk to the glibc
people.
Ian
prev parent reply other threads:[~2004-11-27 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 11:30 Arthur Yang
2004-11-27 2:46 ` Ian Lance Taylor [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=m3brdk3t6x.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=arthuryang@online.cq.cn \
--cc=gcc-help@gcc.gnu.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).