From: "Timothy J. Wood" <tjw@omnigroup.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: 3.4 bootstrap failure on powerpc-apple-darwin7.2.0
Date: Sun, 18 Jan 2004 19:27:00 -0000 [thread overview]
Message-ID: <4AB0211E-49EC-11D8-8B22-0003933F3BC2@omnigroup.com> (raw)
In-Reply-To: <759F3C13-49D0-11D8-9D69-000393A6D2F2@physics.uc.edu>
On Jan 18, 2004, at 8:07 AM, Andrew Pinski wrote:
>
> On Jan 17, 2004, at 20:39, Timothy J. Wood wrote:
>
>>
>> ../gcc/configure --prefix="$PREFIX" --enable-altivec
>> --enable-languages="c,c++,objc"
>
>
> --enable-altivec is really only for ppc linux to enable the altivec
> ABI by default which is
> done for PPC Darwin by default already.
Thanks; could someone update the documentation in install.texi to say
that this should not be passed for PPC Darwin?
> If you remove that you should be able to bootstrap just fine, note
> that the syntax for
> altivec differs for FSF than what the original version of MOT's PEM.
I discovered this last night too, but then Altivec doesn't seem work.
I thought it was because I didn't have --enable-altivec, but I guess
either something is busted or I'm doing something (else) wrong. I'll
send out a new mail on that to change the subject line :)
-tim
next prev parent reply other threads:[~2004-01-18 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 4:39 Timothy J. Wood
2004-01-18 16:07 ` Andrew Pinski
2004-01-18 19:27 ` Timothy J. Wood [this message]
2004-01-18 23:11 ` Ziemowit Laski
2004-01-18 23:18 ` Andrew Pinski
2004-01-18 23:36 ` Ziemowit Laski
2004-01-18 23:45 ` Andrew Pinski
2004-01-21 14:56 ` Segher Boessenkool
2004-01-19 20:57 ` Dale Johannesen
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=4AB0211E-49EC-11D8-8B22-0003933F3BC2@omnigroup.com \
--to=tjw@omnigroup.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).