Summary: | STRANGE - cannot load _any_ plugins (NetBSD) | ||
---|---|---|---|
Product: | [Applications] kopete | Reporter: | Nate Hill <vugdeox> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | thiago |
Priority: | NOR | ||
Version: | 0.7 | ||
Target Milestone: | --- | ||
Platform: | NetBSD pkgsrc | ||
OS: | NetBSD | ||
Latest Commit: | Version Fixed In: |
Description
Nate Hill
2003-08-05 23:17:17 UTC
Subject: Re: [Kopete-devel] New: STRANGE - cannot load _any_ plugins (NetBSD)
On Tuesday 05 August 2003 23:17, Nate Hill wrote:
> kdecore (KLibLoader): WARNING: library=kopete_icq:
> file=/usr/X11R6/lib/kde3/kopete_icq.la: Shared object "kopete_icq.a" not
> found
It installs .la files instead of .so?!? Is this specific for NetBSD?
And why does it need .a (static) libs? Somehow I think the build system is
quite screwed here :(
Does replacing admin/ with something from KDE CVS's kde-common module (notably
KDE_3_1_BRANCH) and rerunning make -f Makefile.cvs and configure help?
You may need to checkout kopete_0_7_branch instead of the release tarballs to
be able to run make -f Makefile.cvs.
I noticed that no .so files where installed. Here is a diff of installed files versus 0.6.2: --- ../kopete-0.6.2/PLIST 2003-07-19 13:50:25.000000000 -0500 +++ ./PLIST 2003-08-05 16:00:04.000000000 -0500 @@ -1,89 +1,121 @@ -@comment $NetBSD: PLIST,v 1.1.1.1 2003/07/19 18:50:25 jmmv Exp $ +@comment $NetBSD$ +bin/kconf_update_bin/kopete-account-kconf_update bin/kopete -bin/winpopup-install.sh -bin/winpopup-send.sh -lib/kde3/kopete_autoaway.a -lib/kde3/kopete_autoaway.la -lib/kde3/kopete_autoaway.so +lib/kde3/kopete_aim.a +lib/kde3/kopete_aim.la +lib/kde3/kopete_autoreplace.a +lib/kde3/kopete_autoreplace.la lib/kde3/kopete_connectionstatus.a lib/kde3/kopete_connectionstatus.la -lib/kde3/kopete_connectionstatus.so lib/kde3/kopete_contactnotes.a lib/kde3/kopete_contactnotes.la -lib/kde3/kopete_contactnotes.so lib/kde3/kopete_cryptography.a lib/kde3/kopete_cryptography.la -lib/kde3/kopete_cryptography.so -lib/kde3/kopete_gadu.a -lib/kde3/kopete_gadu.la -lib/kde3/kopete_gadu.so +lib/kde3/kopete_highlight.a +lib/kde3/kopete_highlight.la +lib/kde3/kopete_history.a +lib/kde3/kopete_history.la lib/kde3/kopete_icq.a lib/kde3/kopete_icq.la -lib/kde3/kopete_icq.so -lib/kde3/kopete_importer.a -lib/kde3/kopete_importer.la -lib/kde3/kopete_irc.a -lib/kde3/kopete_irc.la -lib/kde3/kopete_irc.so -lib/kde3/kopete_jabber.a -lib/kde3/kopete_jabber.la -lib/kde3/kopete_jabber.so lib/kde3/kopete_msn.a lib/kde3/kopete_msn.la -lib/kde3/kopete_msn.so lib/kde3/kopete_nowlistening.a lib/kde3/kopete_nowlistening.la -lib/kde3/kopete_nowlistening.so -lib/kde3/kopete_oscar.a -lib/kde3/kopete_oscar.la -lib/kde3/kopete_oscar.so -lib/kde3/kopete_sms.a -lib/kde3/kopete_sms.la -lib/kde3/kopete_sms.so +lib/kde3/kopete_spellcheck.a +lib/kde3/kopete_spellcheck.la +lib/kde3/kopete_texteffect.a +lib/kde3/kopete_texteffect.la lib/kde3/kopete_translator.a lib/kde3/kopete_translator.la -lib/kde3/kopete_translator.so lib/kde3/kopete_webpresence.a lib/kde3/kopete_webpresence.la -lib/kde3/kopete_webpresence.so -lib/kde3/kopete_wp.a -lib/kde3/kopete_wp.la -lib/kde3/kopete_wp.so +lib/kde3/kopete_yahoo.a +lib/kde3/kopete_yahoo.la +lib/kde3/libkrichtexteditpart.a +lib/kde3/libkrichtexteditpart.la +lib/kde3/libkrichtexteditpart.so lib/libkopete.a lib/libkopete.la -lib/libkopete.so -lib/libkopete.so.1 -lib/libkopete.so.1.0 -lib/libqssl.a -lib/libqssl.la -lib/libqssl.so -lib/libqssl.so.0 -lib/libqssl.so.0.0 +lib/libkopete_oscar.a +lib/libkopete_oscar.la +lib/libkopete_oscar.so +lib/libkopete_oscar.so.0 +lib/libkopete_oscar.so.0.0 share/kde/applnk/Internet/kopete.desktop -share/kde/apps/kopete/autoaway.plugin -share/kde/apps/kopete/connectionstatus.plugin -share/kde/apps/kopete/contactnotes.plugin -share/kde/apps/kopete/cryptography.plugin +share/kde/apps/kconf_update/kopete-account-kconf_update.sh +share/kde/apps/kconf_update/kopete-account-kconf_update.upd +share/kde/apps/kconf_update/kopete-pluginloader.pl +share/kde/apps/kconf_update/kopete-pluginloader.upd +share/kde/apps/kopete/contactnotesui.rc +share/kde/apps/kopete/cryptographyui.rc share/kde/apps/kopete/eventsrc -share/kde/apps/kopete/gadu.plugin -share/kde/apps/kopete/icq.plugin -share/kde/apps/kopete/importer.plugin -share/kde/apps/kopete/irc.plugin -share/kde/apps/kopete/jabber.plugin +share/kde/apps/kopete/historychatui.rc +share/kde/apps/kopete/historyui.rc +share/kde/apps/kopete/icons/hicolor/16x16/actions/admin_icon.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/aim_away.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/aim_offline.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/aim_online.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/aol_icon.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/dt_icon.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/emoticon.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/free_icon.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_away.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_dnd.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_ffc.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_invisible.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_na.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_occupied.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_offline.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/icq_online.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/kopeteavailable.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/kopeteaway.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/metacontact_away.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/metacontact_offline.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/metacontact_online.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/metacontact_unknown.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_away.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_blocked.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_brb.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_busy.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_invisible.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_lunch.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_na.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_offline.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_online.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/msn_phone.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/newmsg.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/status_unknown.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_away.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_busy.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_idle.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_invisible.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_mobile.png +share/kde/apps/kopete/icons/hicolor/16x16/actions/yahoo_tea.png +share/kde/apps/kopete/icons/hicolor/16x16/apps/aim_protocol.png +share/kde/apps/kopete/icons/hicolor/16x16/apps/icq_protocol.png +share/kde/apps/kopete/icons/hicolor/16x16/apps/msn_protocol.png +share/kde/apps/kopete/icons/hicolor/16x16/apps/yahoo_protocol.png +share/kde/apps/kopete/icons/hicolor/22x22/actions/kopeteavailable.png +share/kde/apps/kopete/icons/hicolor/22x22/actions/kopeteaway.png +share/kde/apps/kopete/icons/hicolor/32x32/actions/kopeteavailable.png +share/kde/apps/kopete/icons/hicolor/32x32/actions/kopeteaway.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/aim_protocol.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/autoreplace.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/highlight.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/icq_protocol.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/msn_protocol.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/texteffect.png +share/kde/apps/kopete/icons/hicolor/32x32/apps/yahoo_protocol.png +share/kde/apps/kopete/icons/hicolor/48x48/actions/kopeteavailable.png +share/kde/apps/kopete/icons/hicolor/48x48/actions/kopeteaway.png +share/kde/apps/kopete/icons/hicolor/48x48/apps/yahoo_protocol.png share/kde/apps/kopete/kopetechatwindow.rc +share/kde/apps/kopete/kopeteemailwindow.rc share/kde/apps/kopete/kopeteui.rc -share/kde/apps/kopete/loading.html -share/kde/apps/kopete/msn.plugin -share/kde/apps/kopete/nowlistening.plugin -share/kde/apps/kopete/oscar.plugin -share/kde/apps/kopete/oscar_protocol.png -share/kde/apps/kopete/pics/Makefile.am -share/kde/apps/kopete/pics/addside.png -share/kde/apps/kopete/pics/admin_icon.png -share/kde/apps/kopete/pics/aol_icon.png -share/kde/apps/kopete/pics/away-mobile.png -share/kde/apps/kopete/pics/dt_icon.png -share/kde/apps/kopete/pics/emoticon.png +share/kde/apps/kopete/msnchatui.rc +share/kde/apps/kopete/nowlisteningchatui.rc +share/kde/apps/kopete/nowlisteningui.rc +share/kde/apps/kopete/pics/aim_connecting.mng share/kde/apps/kopete/pics/emoticons/BoxedEmoticonSet/angry.png share/kde/apps/kopete/pics/emoticons/BoxedEmoticonSet/bigsmile.png share/kde/apps/kopete/pics/emoticons/BoxedEmoticonSet/confused.png @@ -116,6 +148,21 @@ share/kde/apps/kopete/pics/emoticons/KMess-Blue/teeth.png share/kde/apps/kopete/pics/emoticons/KMess-Blue/tongue.png share/kde/apps/kopete/pics/emoticons/KMess-Blue/wink.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/angel.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/angry.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/confused.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/cry.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/devil.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/embarrassed.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/emoticons.xml +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/omg.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/sad.png +share/kde/apps/kopete/pics/emoticons/KMess-Cartoon/shade.png Hello, during the configure process, libtool detects your system and decides if it can and will build static or shared libraries. If you take a look at it, you'll find that it said it can't build shared libraries. That's why it only created .a files. Can you please check your config.log and other sources to find out why libtool decided your system doesn't support shared libraries? I understand that but, why don't the static plugins work? Okay, I noticed libtool spitting out a number of warnings that said things needed libkopete.* but I didn't seem to support something or other... Does libtool keep a log? Subject: Re: [Kopete-devel] STRANGE - cannot load _any_ plugins (NetBSD)
On Wednesday 06 August 2003 05:15, Nate Hill wrote:
> I understand that but, why don't the static plugins work?
>
> Okay, I noticed libtool spitting out a number of warnings that said things
> needed libkopete.* but I didn't seem to support something or other...
>
> Does libtool keep a log?
I don't know a whole lot about this low-level stuff, but as far as I
understood it you can never open static libs at runtime through dlopen or
whatever else mechanism, and only shared libs. Static libs don't provide the
required information to dynamically load libs.
Whether this is correct, dunno, it's not my league, but that's how I
understand it :)
Martijn is correct. "Static" and "plugin" are two word that don't go together. In ELF systems, a static library is a collection of .o (relocateable ELF) objects, while a shared library and a loadable module are .so (shared ELF). There are even systems, like Mac OS X where shared libraries and loadable modules are not the same thing either. All that aside, libtool decided that on your system it wouldn't build shared objects. Check your config.log or try re-running configure again, specifying -- enable-shared this time. Sometimes, it's a bit cryptic to detect what decisions libtool made. It could be a libtool bug as well, mind you. Okay, I remember seeing these same messages on other builds I was trying (mabye kopete 0.6.2?). I'll try enable-shared or such... Just seemed like you really shouldn't be allowed to continue a build if you can't build the modules correctly... Okay, it seems that --enable-shared defaults to yes and configure did not fail any tests. What could be the problem? configure:7706: checking if cc PIC flag -fPIC works configure:7730: result: yes configure:7754: checking if cc supports -c -o file.o configure:7795: result: yes configure:7821: checking whether the cc linker (ld) supports shared libraries configure:8604: result: yes configure:8626: checking whether -lc should be explicitly linked in configure:8631: cc -c -DNDEBUG -O2 -O2 -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include -I/usr/X11R6/include con ftest.c >&5 configure:8634: $? = 0 configure:8648: cc -shared -nodefaultlibs conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| grep -lc \>/dev/nul l 2\>\&1 configure:8651: $? = 1 configure:8663: result: yes configure:8669: checking how to hardcode library paths into programs configure:8693: result: immediate configure:8707: checking whether stripping libraries is possible configure:8712: result: yes configure:8719: checking dynamic linker characteristics configure:9170: result: NetBSD ld.elf_so configure:9823: checking if libtool supports shared libraries configure:9825: result: yes configure:9828: checking whether to build shared libraries configure:9849: result: yes configure:9852: checking whether to build static libraries configure:9856: result: no configure:9935: creating libtool configure:10660: checking whether the c++ linker (ld) supports shared libraries configure:11315: result: yes configure:11332: c++ -c -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -I/usr/pkg/include -I/usr/X11R6/include -fno-exceptions -fno-check-new -I/usr/pkg/include -I/usr/X11R6/ include conftest.cc >&5 configure:11335: $? = 0 configure:11435: checking for c++ option to produce PIC configure:11671: result: -fPIC configure:11678: checking if c++ PIC flag -fPIC works configure:11702: result: yes configure:11726: checking if c++ supports -c -o file.o configure:11767: result: yes configure:11793: checking whether the c++ linker (ld) supports shared libraries configure:11815: result: yes configure:11837: checking whether -lc should be explicitly linked in configure:11842: c++ -c -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -I/usr/pkg/include -I/usr/X11R6/include -fno-exceptions -fno-check-new -I/usr/pkg/include -I/usr/X11R6/ include conftest.cc >&5 conftest.cc:1: warning: `int dummy' defined but not used configure:11845: $? = 0 configure:11859: c++ -shared -nostdlib conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| grep -lc \>/dev/null 2\>\&1 configure:11862: $? = 1 configure:11874: result: yes configure:11880: checking how to hardcode library paths into programs configure:11904: result: immediate configure:11918: checking whether stripping libraries is possible configure:11923: result: yes configure:11930: checking dynamic linker characteristics configure:12381: result: NetBSD ld.elf_so configure:16658: checking for msgfmt configure:16685: result: /usr/bin/msgfmt configure:16694: checking for gmsgfmt configure:16725: result: /usr/bin/msgfmt configure:16744: checking for xgettext configure:16771: result: /usr/bin/xgettext Okay, I've finally found some useful output. I'm sure now that this is what needs to be fixed. Anyone know how to fix this: *** Warning: This library needs some functionality provided by -lXss. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have. *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. *** Since this library must not contain undefined symbols, *** because either the platform does not support them or *** it was explicitly requested with -no-undefined, *** libtool will only create a static version of it. This appears in many places during the build (s/-lXss/foo/). How can this be fixed? *** Warning: This library needs some functionality provided by ../../libkopete/libkopete.la. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have. I'm guessing this is a libtool bug. Can you install libtool on your system, then go to Kopete's top source dir, run "libtoolize --force", then re-run configure? Okay, I've isolated the problem some more. The first message is _the_ problem, I only have a static libXss (no idea wtf that is) and libtool builds a static libkopete. Did 0.6.2 use libXss? because, I had no problem with this. I'm contacting some NetBSD developers about this. Subject: Re: [Kopete-devel] STRANGE - cannot load _any_ plugins (NetBSD) On Thursday 07 August 2003 09:54, Nate Hill wrote: > Okay, I've isolated the problem some more. The first message is _the_ > problem, I only have a static libXss (no idea wtf that is) and libtool > builds a static libkopete. Did 0.6.2 use libXss? because, I had no problem > with this. I'm contacting some NetBSD developers about this. I don't know what libXss is either, so I googled around. Ironically the first hit for libxss is... http://mail-index.netbsd.org/netbsd-bugs/2003/01/24/0021.html :) Apart from that all I could find is that it's apparently a lib part of X11, but I have no idea what exactly. No clue what search keywords could help... X ScreenSaver extension, and prolly unrelated to this bug :) Subject: Re: [Kopete-devel] STRANGE - cannot load _any_ plugins (NetBSD) On Thursday 07 August 2003 19:05, sgehn@gmx.net wrote: > X ScreenSaver extension, and prolly unrelated to this bug :) Besides that this is indeed new as our auto-away implementation in 0.6 AFAIK didn't use it (and was a plugin). This surely explains why Nate didn't have the problem before... Yes, I also saw that PR. However, everyone on #Kopete told me they also only had a static version of libXss (find /usr/X11R5 | grep Xss) and they had no problems building. So, I think that Xss is not an issue it's libtool. Anyone know where the libtool experts are? Anyways, I can't see how it could be anything but libtool. Hello, I'm not a libtool hacker, but I've done my share of hacking with it. I might be able to turn up something. Can you take a look at your libtool script inside the kopete top builddir and find the following values for me please: allow_libtool_libs_with_static_runtimes deplibs_check_method file_magic_cmd (if it's "\$MAGIC_CMD", then MAGIC_CMD's value too) Reading our extract of ltmain.sh (which gets included into configure), it seems libtool should choose one of these two values for deplibs_check_method: 'match_pattern /lib[^/]+(\.so\.[0-9]+\.[0-9]+|_pic\.a)$' 'match_pattern /lib[^/]+(\.so|_pic\.a)$' (the first is for non-ELF targets) Anyways, what happened after you ran libtoolize? Okay, you should be aware that I'm doing this using pkgsrc. Everything is "different". I couldn't find anything you asked for, here is libtool: #!/bin/sh # # $NetBSD: libtool.sh,v 1.8 2002/12/26 17:08:57 jlam Exp $ Xsed='/usr/bin/sed -e 1s/^X//' sed_quote_subst='s/\([\\`\\"$\\\\]\)/\\\1/g' private_pre_cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.private-pre-cache" private_cache_add="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-cache-add" private_cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-cache" private_post_cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-post-cache" pre_cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.pre-cache" cache_add="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.cache-add-trans" cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.cache-trans" post_cache="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.post-cache" logic="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.logic-trans" post_logic="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-logic" wrapperlog="/usr/pkgsrc/chat/kopete/work/.buildlink/.wrapper.log" libtool_fix_la="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-fix-la" libtool_do_install="/usr/pkgsrc/chat/kopete/work/.buildlink/bin/.libtool-do-install" fixlibpath=${BUILDLINK_FIX_IMPROPER_LIBTOOL_LIBPATH-yes} updatecache=${BUILDLINK_UPDATE_CACHE-yes} cacheall=${BUILDLINK_CACHE_ALL-no} cat="/bin/cat" echo="echo" test="test" BUILDLINK_DIR="/usr/pkgsrc/chat/kopete/work/.buildlink" BUILDLINK_X11_DIR="/usr/pkgsrc/chat/kopete/work/.buildlink-x11" WRKDIR="/usr/pkgsrc/chat/kopete/work" WRKSRC="/usr/pkgsrc/chat/kopete/work/kopete-0.7" cmd="/usr/pkg/bin/libtool" lafile= case "$1" in *install|*cp|*install-sh|*install.sh) arg="$1"; shift . $libtool_do_install ;; *) while $test $# -gt 0; do arg="$1"; shift case $arg in --fix-la) case "$1" in *.la) lafile="$1" . $libtool_fix_la exit ;; esac ;; --mode|--mode=install) if $test "$arg" = "--mode=install" || \ $test "$arg" = "--mode" -a "$1" = "install"; then . $libtool_do_install break fi ;; -o) case "$1" in *.la) lafile="$1" ;; esac ;; *) cachehit=no skipcache=no . $private_cache case $skipcache,$cachehit in no,no) . $cache ;; esac case $cachehit in no) . $logic ;; esac ;; esac cmd="$cmd $arg" done ;; esac $echo $cmd >> $wrapperlog eval $cmd wrapper_result=$? if $test -n "$lafile" && $test -f "$lafile"; then . $libtool_fix_la fi exit ${wrapper_result} Okay, I've got somewhat of a solution. I don't know if it works entirely yet. I've set ac_cv_lib_Xss_XScreenSaverQueryInfo="no" and It's built a dynamic libkopete. Building plugins atm. Anyways, I'm not sure what affect this will have on the build, does Auto-away _require_ Xss? Even if it doesn't this is just a quick hack and I'll continue trying to find out how I can link against libXss.a. btw, jmmv@NetBSD.org said that I could try linking directly to libXss.a instead of using -lXss, any comments? *** This bug has been marked as a duplicate of 62194 *** |