From: Andrew Cagney <cagney@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: [htdocs patch] Build 64-bit frysk on PPC64
Date: Mon, 20 Nov 2006 15:46:00 -0000 [thread overview]
Message-ID: <4561CDAC.10004@redhat.com> (raw)
In-Reply-To: <dcbde71d0611180515s7b948580pa474539d1bc5a705@mail.gmail.com>
Yao Qi wrote:
>> Mark I agree with your sentiment, unfortunately its not the way autoconf
>> thinks the world works, I have this horrible fealing that, strictly
>> speaking, powerpc64-unknown-linux-gnu needs to also be passed to
>> configure, argh!
>
> Do you mean pass "host=powerpc64-unknown-linux-gnu" to configure?
> powerpc64-unknown-linux-gnu could be detected by configure, but frysk
> is still built in a 32-bit mode, since default mode of powerpc64
> toolchain is to generate 32-bit code, unlike x86_64 toolchain.
>
I'm not sure about the latest syntax, but running configure as:
.../frysk/configure powerpc64-unknown-linux-gnu
was a (wacked-out) requirement when building some of the other gnu
tools, at least for tools that could be cross compiled.
If frysk doesn't need that (I guess 'cos it isn't cross compileable)
then ya!
thanks for the fix,
Andrew
>>
>> Yao, does powerpc64-unknown-linux-gnu also need to be supplied as a
>> parameter to autogen.sh? Either way, yes please add this, and thanks.
>>
> No need to pass "powerpc64-unknown-linux-gnu" to configure, since we
> could build 64-bit frysk
> on ppc64 with "powerpc64-unknown-linux-gnu".
>
> Checked it in.
>
>> Andrew (who wonders what could really be so wrong with wrapping that
>> whole mess up in a -m64 option for frysk's autogen.sh)
>>
>
prev parent reply other threads:[~2006-11-20 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 2:42 Yao Qi
2006-09-05 11:47 ` Mark Wielaard
2006-09-06 6:46 ` Alexandre Oliva
2006-11-17 17:32 ` Andrew Cagney
2006-11-18 13:16 ` Yao Qi
2006-11-20 15:46 ` Andrew Cagney [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=4561CDAC.10004@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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).