Re: [htdocs patch] Build 64-bit frysk on PPC64

[Andrew Cagney <cagney at redhat dot com>]

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.
>
>