[kde-solaris] Compiling 3.1 on Solaris 8 with gcc 3.2

Laurent Blume kde-solaris@mail.kde.org
Wed Feb 12 19:14:07 2003

Did you try with GNU make ?
Sometimes it helps...

As for me, I built QT with QTDIR pointing to the _sources_, and add 
$QTDIR/bin in the beginning of the PATH:
./configure [options]
make install

in [options], I also add all the includes (-I<dir>/include) and the 
necessary link information so LD_LIBRARY_PATH should not be needed at 
all (-L<dir>/lib -R<dir>/lib)

And only after installing, the runtime $QTDIR points to the installation 
The good part of 'make install' is that it installs only useful stuff, 
thus saving a lot of space comparing to building in place as it was in 
previous version. Then, a lot of stuff was left to rot on the disk.


Paul Hands wrote:
> Nick,
> Firstly, thanks for replying so quickly.
> It would seem that I did build QT correctly, then, and it's just the 
> INSTALL file which is making me worry.  It specifically states that 
> after a successful "make", a "make install" installs in the relevant 
> places as defined by prefix(es). 
> I would guess that means that I only have to debug why arts won't 
> compile.   In my case, I have chosen to build everything, including qt 
> in /opt/kde3.1.  Both QTDIR and KDEDIR point there.
> The error seems to be from ld, so it might be a library issue, I guess?  
> I think I have LD_LIBRARY_PATH fairly complete, but if I knew how to 
> decode the actual error message, I might stand a better chance.
> Paul
> On Wed, 2003-02-12 at 16:10, Nick THOMPSON wrote:
>>QT is a build in place application. You should build it where you want
>>it to end up and you don't need a make install.
>>Have you got all the libraries in place? I setup the following
>>environment variables before I do a KDE build (you'll need to adapt them
>>for your setup):
>>export KDEDIR=/opt/kde/3.1
>>export QTDIR=/opt/qt/3.1
>>alias conf='./configure --disable-debug --prefix=/opt/kde/3.1
>>--with-ssl-dir=/opt/openssl --with-extr
>>Any help...?