> Hm, you should try to be more exact when reporting such things...
I'm sorry, I'm normally more precise but the world of autoconf is completely
new to me having only ever used it as an end-user up until a few days ago.
The problem was purely cosmetic - the plugin does compile, but when you run
./configure it shows up as:
checking for licq header files... ./configure: cd: ./../../include: No such
file or directory
"/usr/local/include/licq"
which makes you wonder whether it did actually work (it did work, but it just
looks bad.) The line in acinclude.m4 was:
relpath=`cd $srcdir/../../include && pwd`
which needs to be changed to
relpath=`(cd $srcdir/../../include && pwd) 2> /dev/null`
It appears to be in the admin/acinclude.m4.in file (in the LICQ_CHECK_LICQ
definition - line 60 in the source for v1.2.7) I would've tried searching
there earlier only I didn't realise there even was a .in file!
Cheers,
Adam.
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel
