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

List:       kde-devel
Subject:    Re: meinproc doesn't work
From:       Eric Laffoon <sequitur () easystreet ! com>
Date:       2001-08-16 19:46:35
[Download RAW message or body]

On Wednesday 15 August 2001 01:17 am, Stephan Kulow wrote:
> On Wednesday, 15. August 2001 01:46, Milo Hyson wrote:
> > Meinproc seems to be rather flaky. I have problems compiling kdelibs
> > under FreeBSD because of meinproc. My only workaround is to manually run
> > 'gmake install' on a number of sub-modules including kio, kdeui, kdesu
> > and dcop.
>
> Your problem is not meinproc, but that libtool doesn't set runtime paths
> correctly. That would happen with any KDE binary running within kdelibs
> before installing.
>
> Greetings, Stephan

I'm trying to pin this down. I have a new system install from a while back 
and rebuilt my CVS version of KDE just before the 2.2 release. Everyting was 
fine, then I updated some modules that were less than perfect. Suddenly all 
kinds of things stopped compiling. I started fresh with a new directory and 
set up the environment variables. kdelibs failed! It appeared to be accessing 
ksycoca on my distro install. I set the path and lib path and set it to 
compile again and it worked. Now kdebase gives the same meinproc error!

I seem to remember some semi random problems we had in the past getting 
Quanta to compile on all platforms due to internal KDE configuration files... 
but I can't remember the file that sets the internal paths now.

Pardon me for being a bit dense... but can anyone give any suggestions on how 
to correct this and insure these internal paths are set up? It seems like a 
catch 22 to me as indicated. Are we to build KDE in place now?

TIA

-- 
Eric Laffoon                    sequitur@kde.org
A member of the Quanta+ Web development team
http://quanta.sourceforge.net
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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