LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Friday the 13th Massive Upgrade (https://www.linuxquestions.org/questions/slackware-14/friday-the-13th-massive-upgrade-4175416622/)

rworkman 08-03-2012 10:50 AM

EDIT: well, I guess I should have refreshed the page before replying, but oh well... :)

First of all, I don't see that here:
Code:

[rworkman@liberty ~]$ ldd /usr/bin/curl
        linux-vdso.so.1 (0x00007fff26d82000)
        libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f7ae8fc9000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f7ae8d95000)
        libz.so.1 => /usr/lib64/libz.so.1 (0x00007f7ae8b7f000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f7ae87c2000)
        libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007f7ae8590000)
        liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f7ae8381000)
        libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f7ae8139000)
        libssl.so.1 => /usr/lib64/libssl.so.1 (0x00007f7ae7ed1000)
        libcrypto.so.1 => /usr/lib64/libcrypto.so.1 (0x00007f7ae7af5000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7ae78d9000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7ae9222000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7ae76bf000)
        libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f7ae74a4000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f7ae72a0000)

What isn't immediately obvious though is that curl itself isn't even linked to libssl - ldd shows a recursive list of everything that curl is linked against, everything that those things are linked against, and so on. A better list comes from this:
Code:

[rworkman@liberty ~]$ objdump -p /usr/bin/curl | grep NEEDED
  NEEDED              libcurl.so.4
  NEEDED              librt.so.1
  NEEDED              libz.so.1
  NEEDED              libc.so.6

Now it becomes more clear where the libssl linking is:
Code:

[rworkman@liberty ~]$ objdump -p /usr/lib64/libcurl.so.4 | grep NEEDED
  NEEDED              libidn.so.11
  NEEDED              liblber-2.4.so.2
  NEEDED              libldap-2.4.so.2
  NEEDED              librt.so.1
  NEEDED              libssl.so.1
  NEEDED              libcrypto.so.1
  NEEDED              libz.so.1
  NEEDED              libc.so.6

Of course, none of that answers your initial question. Given how ldd(1) behaves, I suspect that you have an old library still iinked to libssl.so.0 - make sure you didn't miss a package.

matt0512 08-03-2012 11:42 AM

Thank you for your answers. I was sure there had to be a simple answer. Yes, I skipped upgrading openldap-client since I don't need LDAP functions, that was my fault. And I didn't upgrade aaa_elflibs because, as far as I know, the aaa_* packages are intended for one time installation, there's no need to upgrade them.

rworkman 08-03-2012 05:51 PM

If you're going to run -current, you upgrade *all* of the packages upgraded in the tree - don't skip any of them, even aaa_*

lonestar_italy 08-09-2012 04:46 PM

Quote:

Originally Posted by BroX (Post 4727947)
:(
Code:

$ clementine --verbose
Segmentation fault

Recompiling didn't produce any errors, and all libraries are found. Tried moving the config and rc files in ~/ away, but alas.

Amarok plays fine though.

Does anyone know how to get more debug info? The segfault message is all I get.

edit: maybe I should add that this is after today's update

Yes, I have the same issue, on both 32 & 64.
I noticed someone filed a bug report to the coders at http://code.google.com/p/clementine-...detail?id=3078
I think it's related to OpenSSL stepping up from 0.9.8 to 1.0.1, but probably more on Clementine's side rather than on Slackware's side.

alekow 08-10-2012 12:49 AM

Quote:

Originally Posted by lonestar_italy (Post 4750292)
Yes, I have the same issue, on both 32 & 64.
I noticed someone filed a bug report to the coders at http://code.google.com/p/clementine-...detail?id=3078
I think it's related to OpenSSL stepping up from 0.9.8 to 1.0.1, but probably more on Clementine's side rather than on Slackware's side.

No problems with clementine 1.0.1 on current 32-bit here.

lonestar_italy 08-18-2012 07:20 AM

Quote:

Originally Posted by alekow (Post 4750586)
No problems with clementine 1.0.1 on current 32-bit here.

Even right now, after the latest updates?
How did you compile Clementine? SBo slackbuild?

alekow 08-19-2012 09:58 AM

I didn't know there was an updated script on slackbuilds.org. I used, as always, manually modified script for version 0.8.<something> if I remember well. I don't see any significant differences though:

Code:

--- clementine.SlackBuild.new        2012-07-18 09:00:20.000000000 +0200
+++ clementine.SlackBuild        2012-07-30 18:20:21.000000000 +0200
@@ -26,12 +26,12 @@
 
 PRGNAM=clementine
 VERSION=${VERSION:-1.0.1}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-4}
 TAG=${TAG:-_SBo}
 
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
-    i?86) export ARCH=i486 ;;
+    i?86) export ARCH=i686 ;;
    arm*) export ARCH=arm ;;
        *) export ARCH=$( uname -m ) ;;
  esac
@@ -46,7 +46,7 @@
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
 elif [ "$ARCH" = "i686" ]; then
-  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
+  SLKCFLAGS="-O2 -march=i686 -mtune=k8-sse3"
  LIBDIRSUFFIX=""
 elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
@@ -79,22 +79,22 @@
        -DCMAKE_INSTALL_PREFIX=/usr \
        -DLIB_SUFFIX=${LIBDIRSUFFIX} \
        -DMAN_INSTALL_DIR=/usr/man \
-        -DCMAKE_BUILD_TYPE=Release \
-        ..
-  make all CFLAGS="-fPIC" PMFLAGS="-DNEWBUFFER"
+        -DCMAKE_BUILD_TYPE=Release ..
+  make -j3 all CFLAGS="-fPIC" PMFLAGS="-DNEWBUFFER"
  make install DESTDIR=$PKG
 cd ..
 
-for i in 16 32 ; do
+for i in 16 32 64 ; do
  install -m 0644 -D dist/${PRGNAM}_${i}.png \
    $PKG/usr/share/icons/hicolor/${i}x${i}/apps/application-x-clementine.png
 done
+install -m 0644 -D dist/${PRGNAM}.desktop $PKG/usr/share/applications/
 
 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a COPYING Changelog $PKG/usr/doc/$PRGNAM-$VERSION/
+#cp -a TODO $PKG/usr/doc/$PRGNAM-$VERSION/
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install
@@ -102,4 +102,4 @@
 cat $CWD/doinst.sh > $PKG/install/doinst.sh
 
 cd $PKG
-/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-txz}

I'm on Slackware-14_beta1 (plus August 4th updates).

lonestar_italy 10-18-2012 07:15 AM

Quote:

Originally Posted by lonestar_italy (Post 4750292)
Yes, I have the same issue, on both 32 & 64.
I noticed someone filed a bug report to the coders at http://code.google.com/p/clementine-...detail?id=3078
I think it's related to OpenSSL stepping up from 0.9.8 to 1.0.1, but probably more on Clementine's side rather than on Slackware's side.

I have found my solution to this, if anyone interested.
I had an old ffmpeg package by AlienBOB hanging around, 0.8.x, and it was probably linking to some library that changed during the 14RCs weeks.
I compiled a new ffmpeg 0.11 package from SBo and clementine now works flawlessly.


All times are GMT -5. The time now is 04:16 AM.