Re: amd64 as target

[Chuck Robey <chuckr chuckr org>]

Manish Singh wrote:

> On Sun, Mar 28, 2004 at 10:45:52PM -0500, Chuck Robey wrote:
>  
>
> > I'm having a heck of a time trying to get glib and gtk to compile nicely 
> > for the amd64.  The configure script keeps on finding the binaries in 
> > /usr/bin and using them  to make decisions, ones that aren't always 
> > correct... you see, I have to cater to two platform needs, one is the 
> > 323 bit one that you're all very familiar with, but the other one needs 
> > -m64, and isn't really very compatible withthe -m32 bit mode.
> >
> > The use of binaries in /usr/bin is confusing me more, I need someone to 
> > lay out the playing field in 2 different ways: one, let me know, please, 
> > how the binaries (glib-something in /usr/bin) figure in the 
> > configuration) and what the right set of switches is in configure to get 
> > me *both* of the two modes I need to cater to.
> >    
>
> All there is a glib-genmarshal and glib-mkenums, which is just codegen
> stuff. They'll produce the same output regardless of architecture, so
> you only need one.
>
>  
>
> > You see, I tried using "env CFLAGS=-m64 configure 
> > --libdir=/usr/local/lib64" but it fails, telliiimg me that the gcc can't 
> > create executeables.  That was for the 64 bit stuff.  For the 32 bit 
> > stuff, it's bringing in /usr/X11R6/lib64, which is completely wrong for 
> > the 32 bit mode.
> >    
>
> Sounds like you forgot to set PKG_CONFIG_PATH to point to /usr/lib/pkgconfig
> (/usr/lib64/pkgconfig would be the default).
>  
You know, I've loooked around a bit now, just where is the 
PKG_CONFIG_PATH documented?

> If you're going for a dual 32/64-bit setup in the same prefix, I'd recommend
> doing the full install of the 64-bit tree, but only the libdir of the 32-bit
> tree, since the rest should be completely sharable.
>
> -Yosh
>