[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: x86_64, --disable-libsuffix and configure checks
From:       Mantia Andras <amantia () kde ! org>
Date:       2006-04-07 18:05:03
Message-ID: 200604072105.04459.amantia () kde ! org
[Download RAW message or body]

On Friday 07 April 2006 12:20, willem boschman wrote:
> On Friday 07 April 2006 10:14, you wrote:
> > On Friday 07 April 2006 10:47, willem boschman wrote:
> > > Hi,
> > >
> > > I',m trying to build kde (3.5.x) from svn on an x86_64 system
> > > with configure --install=/opt/kde --disable-libsuffix. However
> > > most system libraries are in /usr/lib64 and because of this some
> > > configure checks now faile (KDE_CHECK_PYTHON, KDE_CHECK_SSL).
> > > These checks are using something like
> > > libdirs="/usr/lib$kdelibsuff" to find the library directory and
> > > so are now looking for python or openssl in /usr/lib instead of
> > > /usr/lib64. How do i make this work?
> >
> > Why do you want to use /lib for KDE and not /lib64 as the rest of
> > your system?
> >
> > Andras
>
> unlike kde some other stuff i'm trying to compile won't install to
> lib64 by default, for instance exiv2 which is used by digikam so
> digikam can't find it there (an error in the digikam build really it
> doesn't use exiv2-config as it should)  so i thought to just put kde
> in $kdedir/lib (its in a separate dir so i thought this wouldn't
> matter) but of course this causes the above problem

For almost all software it is possible to use an own specified library 
directory. I just compiled exiv2, so I know it. ;-) See 
configure --help.
Otherwise 64 bit distributions would be a mess.

Andras
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]