Gmp upgrades fine if you tell slackpkg to upgrade it before other things.

slackpkg update
slackpkg upgrade glibc-solibs
slackpkg upgrade glibc*
slackpkg upgrade gmp
slackpkg install-new
slackpkg upgrade-all

1 members found this post helpful.

Yes that's a good point. I shall mention that in top post.

thanks guys for the info. It solved the problem with icons on my slack64-current

Do i have to be 'init 1' when upgrading glibc-solibs with slackpkg?

Will this be delivered as a normal package upgrade? You know, I can tolerate KDE for a while...

Why nobody is surprised that a tool that manages packages depends on a package? I would expect both slackpkg and things like upgradepkg to be as statically linked as possible.

libpng will probably be upgraded hopefully not too far off. The gmp problem is really to do with the order that things are upgraded I think. It doesn't need a new package built but perhaps an extra check in slackpkg to make sure it's upgraded towards the start of the process.

And anyway slackpkg upgrade-all in my opinion is just an added extra convenience. The best way to upgrade would be to keep a mirror locally and use upgradepkg in the correct order I think.

slackpkg and upgradepkg are shell scripts. They can't be statically linked. But they do rely on other tools to work. There's no way to avoid that.

Some fresh updates just released that should help with this issue.

Does this mean that it's a bug in 1.4.1 and not just a matter of recompiling the apps against the new library version then?

I'd have thought that as all those new slackware packages have just been rebuilt and linked against 1.4.1, downgrading to 1.4.0 would make matters worse as we'd no longer be running with the library version they were compiled against.

I'm a little confused by this now.


edit:

Just checked the new libpng.slackbuild and if I'm reading between the lines correctly, it sounds like a lot of the new packages were built against 1.4.0 and then libpng was updated after that. If that's so then I'm a little less confused than I was a few minutes ago.

Forget what Eric said. Theres already an updated libpng in -current. Use that one (along with the other updates).

Yep, will do. Thanks Sahko. I spotted mRgOBLIN's post just after I posted that. I'll throw them on tomorrow when they've propagated through the mirrors.

OK I must have screwed something up last night when I tried the workaround. I tried it again today and all is working, thank you.

I'll try the official fixes when they hit my Slackware-Current mirror.

Well issues solved:

a/coreutils-8.4-i486-2.txz: Rebuilt.
Use --without-gmp, at least for now. We don't want utilities in /bin
requiring a library in /usr/lib{,64} that may not be available.
l/libpng-1.4.1-i486-2.txz: Rebuilt.
Now with less rat.

still have some issue which i assume are related to libpng

i recompiled imlib2 and giblib using the latest slackbuilds but i cannot save png files with scrot (i can save jpg) and i cannot view png files with feh (i can view jpg etc)

will try to figure out if there are some png specific configure options for either of those that need updating

botnet,

Applying 2 patches to Imlib2 fixed the problem with scrot for me. I don't use feh, so I don't know about that. Good luck!

1 members found this post helpful.