Date: Thu, 20 Mar 2008 22:12:01 -0500 From: Novembre <novembre@gmail.com> To: "Derek Ragona" <derek@computinginnovations.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: some problems after upgrading to 7.0-RELEASE Message-ID: <3b47caa90803202012rc963c89l7de5cb3dc827bd49@mail.gmail.com> In-Reply-To: <6.0.0.22.2.20080320184859.026b36a8@mail.computinginnovations.com> References: <3b47caa90803201610i2a81448cwf06cc38245c3c132@mail.gmail.com> <6.0.0.22.2.20080320184859.026b36a8@mail.computinginnovations.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 20, 2008 at 6:51 PM, Derek Ragona <derek@computinginnovations.com> 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/ld-elf.so.1: > Shared object "libgnutls.so.13" not found, required by "smbd" > ===== > Then, I reran pkg_libchk, and voila, errors: > ===== > samba-3.0.28,1: /usr/local/sbin/smbd misses libgnutls.so.13 > samba-3.0.28,1: /usr/local/sbin/smbd misses libgcrypt.so.13 > samba-3.0.28,1: /usr/local/sbin/swat misses libgnutls.so.13 > samba-3.0.28,1: /usr/local/sbin/swat misses libgcrypt.so.13 > ===== > 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 > -DQT_BUILD_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS > -DQT_44_API_QSQLQUERY_FINISH -DQT3_SUPPORT -DQT_MOC_COMPAT > -DQT_RASTER_IMAGEENGINE -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_MMXEXT > -DQT_HAVE_SSE2 -DQT_NO_STYLE_MAC -DQT_NO_STYLE_WINDOWSVISTA > -DQT_NO_STYLE_WINDOWSXP -DQ_INTERNAL_QAPP_SRC -DQT_NO_DEBUG > -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE > -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 libgnutls.so.13 which I don't have, but I do have a libgnutls.so.26 and libgnutls.so in /usr/local/lib/ (the latter is a symlink to the former). Also, libgnutls.so.15 exists in /usr/local/lib/compat/pkg/. So what I did was creating a symlink to libgnutls.so.26 and called it libgnutls.so.13, 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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3b47caa90803202012rc963c89l7de5cb3dc827bd49>