Date: Mon, 08 Feb 2010 22:08:56 +0100 From: Heino Tiedemann <rotkaps_spam_trap@gmx.de> To: freebsd-questions@freebsd.org Cc: freebsd-ports@freebsd.org, kde-freebsd@freebsd.kde.org Subject: Re: [WORKAROUND] Re: /usr/ports/x11-toolkits/qt33: /usr/bin/ld: warning: libjpeg.so.10, needed by /usr/local/lib/libqt-mt.so, not found (try using -rpath or -rpath-link) Message-ID: <e5b647-ia2.ln1@news.hansenet.de> References: <4B6D40B4.70203@mail.zedat.fu-berlin.de> <20100206124952.34cb5f1d@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ion-Mihai Tetcu <itetcu@FreeBSD.org> wrote: > On Sat, 06 Feb 2010 11:13:08 +0100 > "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> wrote: > >> Since yesterday's portsnape and attempt updating my ports, ALL >> FreeBSD boxes (running FreeBSD 8.0/amd64) fail to update ports via >> 'portmaster -av' at the same point with the following error. >> >> It seems that that port jpeg-8 has been updated and now offering >> libjpeg.so.11 instead of the desired old libjpeg.so.10, so I guess >> everything depending on port jpeg-8 needs to be rebuild - but >> ports/UPDATE does not reflect this. >> >> c++ -fno-exceptions -Wl,-rpath,/usr/local/lib >> -Wl,-rpath,/usr/local/lib -pthread -o ../../../bin/uic >> .obj/release-shared-mt/main.o .obj/release-shared-mt/uic.o >> .obj/release-shared-mt/form.o .obj/release-shared-mt/object.o >> .obj/release-shared-mt/subclassing.o .obj/release-shared-mt/embed.o >> .obj/release-shared-mt/widgetdatabase.o >> .obj/release-shared-mt/domtool.o .obj/release-shared-mt/parser.o >> -L/usr/local/lib -L/usr/local/lib > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> -L/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/lib >> -L/usr/local/lib -lqt-mt -lmng -ljpeg -lpng -lz -lXi -lXrender >> -lXrandr -lXcursor -lXinerama -lXft -lfreetype -lfontconfig -lXext >> -lX11 -lm -lSM -lICE >> /usr/bin/ld: warning: libjpeg.so.10, needed by >> /usr/local/lib/libqt-mt.so, not found (try using -rpath or >> -rpath-link) /usr/local/lib/libqt-mt.so: undefined reference to >> `jpeg_start_decompress@LIBJPEG_7.0' > > > That above it's the problem, kde team is aware of it. > > For the moment the workaround, when you get to this, is to: > mv /usr/local/lib/libqt-mt.so /usr/local/lib/libqt-mt.so.old && \ > cd /usr/ports/x11-toolkits/qt33/ && make && \ > mv /usr/local/lib/libqt-mt.so.old /usr/local/lib/libqt-mt.so && \ > portmaster -C x11-toolkits/qt33 > > > I did this yesterday while under KDE3 without problems. it ssems to be the workaround from UPDATING ,---- | > 20100205: | > AFFECTS: users of qt 3 and kde 3 | > AUTHOR: itetcu@FreeBSD.org | > | > When building qt33 and kdelibs3 (at least), while they are installed, because | > of -L/usr/local/lib being passed too soon, the currently installed libs are | > used instead of the ones from the build. This makes the build fail if you | > updated any of the libs this qt / kde libs are linked against (like libjpeg). | > | > For the moment the workaround, when you get to this, is to move the old lib | > out of the way, e.g.: | > mv /usr/local/lib/libqt-mt.so /usr/local/lib/libqt-mt.so.old && \ | > cd /usr/ports/x11-toolkits/qt33/ && make && \ | > mv /usr/local/lib/libqt-mt.so.old /usr/local/lib/libqt-mt.so && \ | > portmaster -C x11-toolkits/qt33 | > (or portupgrade -w qt-33\*), etc. `---- Has to do with the jpeg update, like writtebn in the discusuion "massive portpgrade" Now my question: Am I the weird kid, if i do NOT have some problems? My qt und kde kompiled fine. No problems. DO Ihave to do the step, mentioned above? Heino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e5b647-ia2.ln1>