* [htdocs patch] Build 64-bit frysk on PPC64
@ 2006-09-05 2:42 Yao Qi
2006-09-05 11:47 ` Mark Wielaard
0 siblings, 1 reply; 6+ messages in thread
From: Yao Qi @ 2006-09-05 2:42 UTC (permalink / raw)
To: frysk
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
It is a little different on PPC64 to build a 64-bit frysk. This patch
adds some instructions for building 64-bit frysk on
htdocs/build/index.html.
Free to tell me if ChangeLog is needed here.
OK to commit? Thanks!
--
Yao Qi
[-- Attachment #2: htdoc.ppc64.patch --]
[-- Type: text/plain, Size: 785 bytes --]
Index: htdocs/build/index.html
===================================================================
RCS file: /cvs/frysk/htdocs/build/index.html,v
retrieving revision 1.105
diff -u -r1.105 index.html
--- htdocs/build/index.html 24 Aug 2006 22:55:41 -0000 1.105
+++ htdocs/build/index.html 5 Sep 2006 02:31:49 -0000
@@ -220,10 +220,22 @@
</pre>
<h3>Configure and Build</h3>
-
+<dd>
+<li> On X86 or X86_64.
<pre>
$ ( mkdir build && cd build && ../frysk/autogen.sh && make -j2 )
</pre>
+</li>
+
+<li> On PPC64.
+<pre>
+$ ( export PKG_CONFIG_PATH=/usr/lib64/pkgconfig )
+$ ( mkdir build && cd build )
+$ ( CC='gcc -m64' GCJ='gcj -m64' GCJLINK='gcj -m64' CXX='g++ -m64' ../frysk/autogen.sh )
+$ ( make -j2 )
+</pre>
+</li>
+</dd>
<h3>Verify the build environment (optional)</h3>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [htdocs patch] Build 64-bit frysk on PPC64
2006-09-05 2:42 [htdocs patch] Build 64-bit frysk on PPC64 Yao Qi
@ 2006-09-05 11:47 ` Mark Wielaard
2006-09-06 6:46 ` Alexandre Oliva
0 siblings, 1 reply; 6+ messages in thread
From: Mark Wielaard @ 2006-09-05 11:47 UTC (permalink / raw)
To: Yao Qi; +Cc: frysk
On Tue, 2006-09-05 at 10:42 +0800, Yao Qi wrote:
> It is a little different on PPC64 to build a 64-bit frysk. This patch
> adds some instructions for building 64-bit frysk on
> htdocs/build/index.html.
> [...]
> +$ ( export PKG_CONFIG_PATH=/usr/lib64/pkgconfig )
> +$ ( mkdir build && cd build )
> +$ ( CC='gcc -m64' GCJ='gcj -m64' GCJLINK='gcj -m64' CXX='g++ -m64' ../frysk/autogen.sh )
The idea seems to be that we always want a 64 bit version of frysk when
we are on ppc64 (and 32bit ppc isn't supported atm it seems). So doesn't
it make more sense to adapt autogen to recognizes this and put in the
right flags by default? Then the user doesn't need to remember any
special flags while building.
Cheers,
Mark
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [htdocs patch] Build 64-bit frysk on PPC64
2006-09-05 11:47 ` Mark Wielaard
@ 2006-09-06 6:46 ` Alexandre Oliva
2006-11-17 17:32 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Alexandre Oliva @ 2006-09-06 6:46 UTC (permalink / raw)
To: Mark Wielaard; +Cc: Yao Qi, frysk
On Sep 5, 2006, Mark Wielaard <mark@klomp.org> wrote:
> On Tue, 2006-09-05 at 10:42 +0800, Yao Qi wrote:
>> It is a little different on PPC64 to build a 64-bit frysk. This patch
>> adds some instructions for building 64-bit frysk on
>> htdocs/build/index.html.
>> [...]
>> +$ ( export PKG_CONFIG_PATH=/usr/lib64/pkgconfig )
>> +$ ( mkdir build && cd build )
>> +$ ( CC='gcc -m64' GCJ='gcj -m64' GCJLINK='gcj -m64' CXX='g++ -m64' ../frysk/autogen.sh )
> The idea seems to be that we always want a 64 bit version of frysk when
> we are on ppc64 (and 32bit ppc isn't supported atm it seems). So doesn't
> it make more sense to adapt autogen to recognizes this and put in the
> right flags by default? Then the user doesn't need to remember any
> special flags while building.
This is generally not something for autogen or the package's own build
machinery, but rather for the RPM build machinery. The reason is that
the package itself should do build as closely as possible to what the
user asks, without making surprising changes behind the user's back.
There are presumably ppc systems that don't include 64-bit support,
libraries, etc, so it would just break the build to try to default to
that, especially if the system itself claims to be ppc not ppc64.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [htdocs patch] Build 64-bit frysk on PPC64
2006-09-06 6:46 ` Alexandre Oliva
@ 2006-11-17 17:32 ` Andrew Cagney
2006-11-18 13:16 ` Yao Qi
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2006-11-17 17:32 UTC (permalink / raw)
To: Alexandre Oliva, Mark Wielaard, Yao Qi; +Cc: frysk
Alexandre Oliva wrote:
> On Sep 5, 2006, Mark Wielaard <mark@klomp.org> wrote:
>
>
>> On Tue, 2006-09-05 at 10:42 +0800, Yao Qi wrote:
>>
>>> It is a little different on PPC64 to build a 64-bit frysk. This patch
>>> adds some instructions for building 64-bit frysk on
>>> htdocs/build/index.html.
>>> [...]
>>> +$ ( export PKG_CONFIG_PATH=/usr/lib64/pkgconfig )
>>> +$ ( mkdir build && cd build )
>>> +$ ( CC='gcc -m64' GCJ='gcj -m64' GCJLINK='gcj -m64' CXX='g++ -m64' ../frysk/autogen.sh )
>>>
>
>
>> The idea seems to be that we always want a 64 bit version of frysk when
>> we are on ppc64 (and 32bit ppc isn't supported atm it seems). So doesn't
>> it make more sense to adapt autogen to recognizes this and put in the
>> right flags by default? Then the user doesn't need to remember any
>> special flags while building.
>>
>
>
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!
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.
Andrew (who wonders what could really be so wrong with wrapping that
whole mess up in a -m64 option for frysk's autogen.sh)
> This is generally not something for autogen or the package's own build
> machinery, but rather for the RPM build machinery. The reason is that
> the package itself should do build as closely as possible to what the
> user asks, without making surprising changes behind the user's back.
> There are presumably ppc systems that don't include 64-bit support,
> libraries, etc, so it would just break the build to try to default to
> that, especially if the system itself claims to be ppc not ppc64.
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [htdocs patch] Build 64-bit frysk on PPC64
2006-11-17 17:32 ` Andrew Cagney
@ 2006-11-18 13:16 ` Yao Qi
2006-11-20 15:46 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Yao Qi @ 2006-11-18 13:16 UTC (permalink / raw)
To: frysk
> 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.
>
> 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)
>
--
Yao
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [htdocs patch] Build 64-bit frysk on PPC64
2006-11-18 13:16 ` Yao Qi
@ 2006-11-20 15:46 ` Andrew Cagney
0 siblings, 0 replies; 6+ messages in thread
From: Andrew Cagney @ 2006-11-20 15:46 UTC (permalink / raw)
To: Yao Qi; +Cc: frysk
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)
>>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-11-20 15:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-09-05 2:42 [htdocs patch] Build 64-bit frysk on PPC64 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 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).