Reposted since I didn't see it in Licq's mailing list archive. I apologize 
if I missed it.


On Tue, 25 Feb 2003, Phillip Pi wrote:

> Thanks Adrian. I will try again if I am super bored. ;) For now, I will
> just wait for the Fink's release of qt3-dev package.
> 
> However, I did get an e-mail reply from Mr. Reed who is maintains qt3 
> packages for Fink. I asked him for a release date of qt3-dev and about 
> Licq compilation issue we ran into. Here's his reply:
> 
> I'm really not sure -- the problem is I can't put qt3 in stable without
> breaking kde 3.0.7, which means that both qt and kde have to be ready  
> to move over.  KDE can't move over until the whole libpng/libpng3 thing
> gets totally resolved.  As far as I'm aware, that's pretty close, but  
> all those things need to be moved to stable before KDE can.            
>                                                                        
> (take 2)                                                               
> After looking at the thread, I'm not really sure what the problem is,  
> though.  I didn't see any config.log entries that say what the actual  
> problem is when it's looking for Qt.                                   
>                                                                        
> (take 3)                                                               
> OK, I just unpacked licq, the problem is that the licq folks are doing 
> their tests for Qt in a non-portable way.  =)                          
>                                                                        
> They're doing stuff like 'if test -r "$qt_dir/libqt-mt.so"' -- on      
> darwin they're libqt-mt.dylib, so the test fails.  They're either going
> to have to add a hack to also look for .dylib (and .sl on HPUX, and,   
> and...) or they should change the checks to do an actual link to find  
> the library.  autoconf should have facilities to do those tests already
> 
> 
> Maybe this helps for you, Licq developers. :)

> On Tue, 25 Feb 2003, Adrian Bool wrote:
> 
> > 
> > Ok, I got the dl library API from,
> > 
> > http://fmri.ucsd.edu/Afni_macx.htm
> > 
> > In order for it complile cleanly I needed to change 'enum bool' on lines
> > 82 and 86 of dlopen.c to 'DYLD_BOOL'.  Bools are always right pain in the
> > ass ;-)
> > 
> > Searching on google does bring up other versions of this dlcompat library.
> > In particualr one there is one on the Darwin CVS server - may be a better
> > one to go for...
> > 
> > Once this is installed, in order to link this with QT you need to add
> > '-ldl' to mkspecs/darwin-g++/qmake.conf on line 57,
> > 
> >     QMAKE_LIBS_DYNLOAD      = -ldl
> > 
> > Once this is all done QT should be able to compile.
> > 
> > Now, licq should be able to be complied. You may need to insert a '-ldl'
> > in qt-gui's Makefile to that to work - can't remember for sure.
> > 
> > But, as i said before even after it has all built cleanly licq does not as
> > it will not load the libraries... May have another go at that next week.
> > 
> > Have fun,
> > 
> > aid
> > 
> > 
> >  On Tue, 25 Feb 2003, Adrian Bool wrote:
> > 
> > >
> > > Yeah, MacOS X does not have dlopen and friends natively.  There is a
> > > dlcompat library that will give you these.  Can't find the URL right now
> > > (at work now and the mac is at home...)  Apache has a dlopen libraray as
> > > well which may help.
> > >
> > > However I did manage to compile all of QT and licq last night, but it
> > > still would not work as licq could not load the qt-gui shared library.
> > > Pain in the ass Apple using some different library API :-/
> > >
> > > I had a look at solving it but got tired and went to bed... Away for a few
> > > days now so problay won't be able to have another look at it for a while.
> > > I'll email you what I did last night this evening when I am back with
> > > the mac...
> > >
> > > Regards,
> > >
> > > aid
> > >
> > > On Tue, 25 Feb 2003, Phillip Pi wrote:
> > >
> > > > Aaron, qt tried to compile with your suggestion. It took a while (not sure
> > > > how long since I went to bed hehe) even on a PowerBook G4 1 Ghz with 512
> > > > MB of RAM. :P
> > > >
> > > > The result was still a show stopper (I hope this is enough paste from the
> > > > end):
> > > >
> > > > ld: warning multiple definitions of symbol _glGetColorTableEXT
> > > > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib(gll_api.o)
> > > > definition of _glGetColorTableEXT
> > > > /usr/X11R6/lib/libGL.dylib(dri_dispatch.o) definition of
> > > > _glGetColorTableEXT
> > > > ld: warning multiple definitions of symbol _glGetColorTableParameterfvEXT
> > > > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib(gll_api.o)
> > > > definition of _glGetColorTableParameterfvEXT
> > > > /usr/X11R6/lib/libGL.dylib(dri_dispatch.o) definition of
> > > > _glGetColorTableParameterfvEXT
> > > > ld: warning multiple definitions of symbol _glGetColorTableParameterivEXT
> > > > /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib(gll_api.o)
> > > > definition of _glGetColorTableParameterivEXT
> > > > /usr/X11R6/lib/libGL.dylib(dri_dispatch.o) definition of
> > > > _glGetColorTableParameterivEXT
> > > > ld: Undefined symbols:
> > > > _dlclose
> > > > _dlopen
> > > > _dlsym
> > > > make[2]: *** [../lib/libqt.dylib.3.1.1] Error 1
> > > > make[1]: *** [sub-src] Error 2
> > > > make: *** [init] Error 2
> > > >
> > > > Aaron, did you get this too?



-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
LICQ-Main mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-main

Reply via email to