some problems after upgrading to 7.0-RELEASE

Novembre novembre at
Thu Mar 20 20:12:03 PDT 2008

On Thu, Mar 20, 2008 at 6:51 PM, Derek Ragona
<derek at> wrote:
>  At 06:10 PM 3/20/2008, Novembre wrote:
> Hi all,
>  I have a couple of questions regarding my upgrade from 6.2-RELEASE to
>  7.0-RELEASE following the instructions from the handbook step by step.
>  After the upgrade, I made a custom kernel, and the only option I've
>  added to /etc/make.conf is " CPUTYPE?=prescott ".
>  1) First question: I upgraded all the ports using " portupgrade -faP
>  ". During this process, I realized that some old libraries were being
>  moved to /usr/local/lib/compat/ (if I'm not mistaken). After all that,
>  I installed the port /sysutils/bsdadminscripts and checked the
>  integrity of the system using pkg_libchk. It didn't produce any
>  warnings or errors, so I assumed that all the freshly installed
>  programs are going to use the correct 7.0 libraries and no library is
>  missing. However, when I rebooted to check whether everything is okay
>  or not, I saw the following:
>  =====
>  Starting smbd.
>  /libexec/
>  Shared object "" not found, required by "smbd"
>  =====
>  Then, I reran pkg_libchk, and voila, errors:
>  =====
>  samba-3.0.28,1: /usr/local/sbin/smbd misses
>  samba-3.0.28,1: /usr/local/sbin/smbd misses
>  samba-3.0.28,1: /usr/local/sbin/swat misses
>  samba-3.0.28,1: /usr/local/sbin/swat misses
>  =====
>  What could have happened during this reboot? I have no idea why
>  pkg_libchk didn't report the missing libraries before the reboot! How
>  can I fix this?
>  2) Second question:  The port upgrading process caused some errors,
>  since a couple of the ports could not be upgraded. I manually upgraded
>  them afterwards except " qt4-gui " which failed to compile. Here's the
>  error:
>  =====
>  c++ -c -O2 -fno-strict-aliasing -pipe -march=prescott -I.
>  -I../../include/Qt -I/usr/local/include -fno-exceptions -D_REENTRANT
>  -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -O2
>  -fno-strict-aliasing -pipe -march=prescott -Wall -W -fPIC -DQT_SHARED
>  -I/usr/local/share/qt4/mkspecs/freebsd-g++ -I. -I../../include/QtCore
>  -I../../include/QtCore -I../../include -I../../include/QtGui
>  -I/usr/local/include/freetype2 -I../3rdparty/harfbuzz/src -Idialogs
>  -I.moc/release-shared -I/usr/local/include -I.uic/release-shared
>  -I/usr/local/include -o .obj/release-shared/qpainter.o
>  painting/qpainter.cpp
>  painting/qpainter.cpp: In member function 'void
>  QPainter::drawPixmap(const QRectF&, const QPixmap&, const QRectF&)':
>  painting/qpainter.cpp:4260: error: 'struct QBrushData' has no member
>  named 'forceTextureClamp'
>  painting/qpainter.cpp: In member function 'void
>  QPainter::drawImage(const QRectF&, const QImage&, const QRectF&,
>  Qt::ImageConversionFlags)':
>  painting/qpainter.cpp:4432: error: 'struct QBrushData' has no member
>  named 'forceTextureClamp'
>  painting/qpainter.cpp: In function 'void qt_format_text(const QFont&,
>  const QRectF&, int, const QTextOption*, const QString&, QRectF*, int,
>  int*, int, QPainter*)':
>  painting/qpainter.cpp:6138: warning: overflow in implicit constant
> conversion
>  *** Error code 1
>  Stop in
> /usr/ports/x11-toolkits/qt4-gui/work/qt-x11-opensource-src-4.3.4/src/gui
>  .
>  *** Error code 1
>  Stop in /usr/ports/x11-toolkits/qt4-gui.
>  *** Error code 1
>  Stop in /usr/ports/x11-toolkits/qt4-gui.
>  ** Command failed [exit code 1]: /usr/bin/script -qa
>  /tmp/portupgrade.7257.30 env UPGRADE_TOOL=portupgrade
>  UPGRADE_PORT=qt4-gui-4.3.0_2 UPGRADE_PORT_VER=4.3.0_2 make
>  ** Fix the problem and try again.
>  =====
>  So I couldn't upgrade that to the latest version (4.3.3), but I did a
>  force upgrade using packages by " portupgrade -PP qt4-gui " and it
>  went from 4.3.0_2 to 4.3.1. So the first question is why compiling the
>  latest version of qt4-gui fails?
>  Thanks a lot
>  Looks like not all ports were properly upgraded.  This can happen when you
> multiple versions of a port installed, or other issues like your ports
> source code not being sane for a particular port.  I would delete /usr/ports
> and cvsup to get a current copy and then try rebuilding samba and any other
> ports you are having problems with.
>  Remember to do recursive rebuilding of dependencies to be sure they are all
> rebuilt too.
>          -Derek

Well, I just followed what's in the handbook and the release notes
step by step, and before doing a full portupgrade, I did a " portsnap
fetch " and " portsnap update " to freshen up my ports tree. And as
far as I know (and I'm pretty sure) I didn't have multiple versions of
any ports installed...

Anyhow, smbd was looking for which I don't have, but I
do have a and in /usr/local/lib/ (the
latter is a symlink to the former). Also, exists in
/usr/local/lib/compat/pkg/. So what I did was creating a symlink to and called it, and after rebooting,
smbd starts just fine. I don't know whether I'm allowed to do such a
thing or not, but since I didn't get any error message while upgrading
samba, I don't know what could have gone wrong...

Any ideas? :)

Thanks a lot...

More information about the freebsd-questions mailing list