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

List:       kde-commits
Subject:    Re: kdebase/kcontrol/crypto
From:       Waldo Bastian <bastian () kde ! org>
Date:       2002-12-15 19:45:53
[Download RAW message or body]

On Sunday 15 December 2002 18:30, David Faure wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 14 December 2002 04:29, Mickael Marchand wrote:
> > CVS commit by marchand:
> >
> > Fix ordering paths problem :
> > test case : have openssl-includes installed in /usr , $all_includes
> > probably contains /usr/include, and sets configure to use your openssl
> > from /usr/local/, configure flags have to be in first place so that it
> > uses the right includes.
>
> Test case that this commit breaks:
> * have openssl in /usr, installed by your distribution
> * have KDE 2 in /usr, installed by your distribution
> * have KDE-CVS in /opt/kde3, /usr/local/kde or whereever else
> Then you don't want SSL includes before KDE includes...
> And IMHO this is a case that happens MUCH more often (for us KDE
> developers) than having our own version of openssl in /usr/local (and
> another version of openssl in /usr, right? Otherwise it wouldn't be a
> problem for you...)
>
> PS: This has been discussed countless times already...... See
> kdelibs/kio/kssl/Makefile.am ...

Wasn't the solution for this that /usr/include should never be added as part 
of a configure check? E.g. if openssl-includes are found in /usr/include, it 
shouldn't add that to $all_includes.

Cheers,
Waldo
-- 
bastian@kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian@suse.com

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