summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorIon-Mihai Tetcu <itetcu@FreeBSD.org>2010-02-06 11:16:25 +0000
committerIon-Mihai Tetcu <itetcu@FreeBSD.org>2010-02-06 11:16:25 +0000
commit391e37898941f550c66d3a18d248b489be8ed70e (patch)
tree1effb73f5f7cb35473ea123142ec0de97a52ac31 /UPDATING
parentUpdate to 1.5.3 (diff)
Add a note for a workaround for at 3 and kde 3 linking against own installed
libs.
Notes
Notes: svn path=/head/; revision=249330
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING17
1 files changed, 17 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index e3d769963962..e1725d5553fe 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,23 @@ You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
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 passedd to 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.
+
+20100205:
AFFECTS: users of lang/perl*
AUTHOR: skv@FreeBSD.org