Re: Re: Ogle on x86-64 build fix

Fri Dec 10 2004, Matthias Saou wrote:
> H}kan Hjort wrote :
> 
> > I'm not sure how other applications deal with this, my personal oppinion
> > is that the whole system is just broken. Libraries are installed in
> >  /lib subdirectories, not /lib64.
> 
> Well, with autotools, they're installed in whatever --libdir was specified
> at compile time. Later on though, something like a "foo-config --libs"
> script to call or a pkgconfig .pc file are needed to avoid checking all
> possible locations.
> 
It's not just all possible locations, since we can't tell just by precens
that it's ok to use it...

> I guess you mean for example the /usr/lib/sse2 directory on Fedora Core?
> That's a different matter IMHO, which arises when the program doesn't
> properly runtime detect CPU optimizations, or when compiling in the opts
> vs. letting runtime detection enable them induces a performance cost.
> 
So, if that can be handled why can this 32 vs 64 code issue? 

> > That a side, I'd appreciate tips on how this is solved in other 
> > configure.in/ac files.
> > 
> > The lib vs lib64 isn't really based on host os but rather if gcc/ld
> > defaults to (or has been given extra flags) to produce 32- or 64-bit
> > code.
> > 
> > www.gnu.org seems to be down, so I can't even checked what if anything
> > the autoconf guys have to say on this.
> 
> Maybe pkgconfig-enabling libdvdread and ogle would make things much easier?
> 
I don't see how.  We don't know if GCC defaults to 32bit code or 64bit code.
We don't know if the user has given some extra flags to GCC to generate something
other than default code (switching to/from 32bit code).  Using a pkg-config
solution basicly means that the user is expected to have the correct path setup.
I.e. if libdvdread has been installed both as a 32bit version and a 64bit version
it had better be in two different prefixes and the correct one for the wanted
code mode (32/64) should be (first) in the PATH.

And still for packages we depend on, libjpeg, libmad liba52 etc. would also
need to be package-configed.

What I'm looking for is some config macros that I can use, not having to write
a bunch of new test from scratch.

We'll see...

/Håkan