Things That Won't Run in -Current (21 April 2015).

Alien Bob · 05-20-2015, 04:45 AM

Debian are using this patch for mumble to overcome the compilation issue with gcc 4.9:

http://bazaar.launchpad.net/~ubuntu-...h-gcc-4.9.diff

ppr:kut · 05-20-2015, 06:12 AM

You don't need to modify anything. All you need to do is specify another environment variable like you already do with CFLAGS. For example like this

Code:

CC=clang \
CFLAGS="$SLKCFLAGS" \
./configure \

cmake knows the CMAKE_C_COMPILER and CMAKE_CXX_COMPILER flags to achieve the same.

kingbeowulf · 05-22-2015, 10:53 AM

Quote:

Originally Posted by ppr:kut

You don't need to modify anything. All you need to do is specify another environment variable like you already do with CFLAGS. For example like this

cmake knows the CMAKE_C_COMPILER and CMAKE_CXX_COMPILER flags to achieve the same.

Now THAT'S a consise answer I can use to get me looking in the right direction. I'll ty it and see if it introduces any unintended weirdness.

kingbeowulf · 05-22-2015, 10:58 AM

Quote:

Originally Posted by Alien Bob

Debian are using this patch for mumble to overcome the compilation issue with gcc 4.9:

http://bazaar.launchpad.net/~ubuntu-...h-gcc-4.9.diff

This is a fairly old patch. My Launchpad search-fu is poor (or else I avoid Debian and Ubuntu like a plague!). I'm curious why there is no mention upstream, that I found so far, in the mumble forums. Surely, they would have bumped into this by now?

Edit: Found unanswered post on Mumble forum with the same error: http://forums.mumble.info/viewtopic....=compile#p5821

kingbeowulf · 05-22-2015, 01:04 PM

To compile mumble-1.2.8 on Slackware-current both clang and the fix-compile-with-gcc-4.9 patch Alien Bob pointed me to were required. From what I have observed:

the patch fixes a bug in Mumble in src/OSS.cpp that earlier gcc versions, and this one, ignores. Clang appears more strict.
clang exits with error without the patch at "short buffer[iMicLength];" in src/OSS.cpp
gcc-4.9.2 (g++) still fails with "internal compiler error" at src/ACL.cpp with the path.

So we still have and issue with either mumble, gcc-4.9.2 or both. Debian must have patched something else for gcc or don't know how to properly annotate their patches...

(BTW, ppr:kut, for mumble it is: QMAKE_CC=clang QMAKE_CXX=clang)

ppencho · 05-24-2015, 12:54 AM

Quote:

Originally Posted by ppencho

Someone else with immediate X/KDE crash when steam-client is being launched?

On clean current32 install (AlienBob slackware-current-install-dvd.iso 17-05-2015 with only additional package installed steamclient-1.0.0.50) I had the same X crash. Installing the latest proprietary AMD driver (Catalyst 14.12 / 14.501.1003) fixed the issue and now steam starts fine.

414N · 05-24-2015, 03:55 AM

I just stumbled upon this issue, where the panels for "Result grid" and "Action output" show nothing upon running a query.
This issue is related to a glib update (>=2.42) that got fixed some time ago and is indeed fixed in the 6.2.5 source, but it resurfaces if you don't upgrade also the glib C++ bindings used by the program, namely glibmm (and cairomm too, as it depends on it). I just upgraded them to version 2.42.0 (glibmm) and 1.11.2 (cairomm) and mysql-workbench is finally working fine again.

ponce · 05-24-2015, 04:09 AM

Quote:

Originally Posted by 414N

I just upgraded them to version 2.42.0 (glibmm) and 1.11.2 (cairomm) and mysql-workbench is finally working fine again.

I updated them one month ago in my personal repository for current

http://cgit.ponce.cc/slackbuilds/commit/?h=cairomm
http://cgit.ponce.cc/slackbuilds/commit/?h=glibmm

alejandro.mc · 05-24-2015, 04:24 AM

I'm no expert, but shouldn't things like Seamonkey, Skype, etc. that I had working perfectly under Debian 7, work out of the box in Debian 8?

Didier Spaier · 05-24-2015, 04:40 AM

Quote:

Originally Posted by alejandro.mc

I'm no expert, but shouldn't things like Seamonkey, Skype, etc. that I had working perfectly under Debian 7, work out of the box in Debian 8?

Thi is not a Debian forum but f I extrapolate most of the time the answer could be no, because for instance the needed shared objects shipped in the distribution have changed, unless all dependencies be bundled. Furthermore why upgrade your distribution if you don't want upgraded applications?

willysr · 05-24-2015, 09:53 AM

Quote:

Originally Posted by ponce

I updated them one month ago in my personal repository for current

http://cgit.ponce.cc/slackbuilds/commit/?h=cairomm
http://cgit.ponce.cc/slackbuilds/commit/?h=glibmm

Ponce, you might want to upgrade pangomm to 2.36.0

ponce · 05-24-2015, 10:56 AM

thanks willy, I'll do.
now I don't remember why I haven't do it already, I seem to recall to have tested it with the other *mm stuff and to have left it out intetionally...
well, maybe it will come to mind.

staus · 05-28-2015, 02:12 PM

I'm mot sure if anyone posted a complaint about Imagemagick. I did a search on the forum, but couldn't find anything.
I had to recompile the 14.1 source code (32 bit) while actually using the current 32 bit Slackware.

I no longer get "Illegal command" failures when running import.

Paulo2 · 05-30-2015, 01:38 PM

Quote:

Originally Posted by staus

I'm mot sure if anyone posted a complaint about Imagemagick. I did a search on the forum, but couldn't find anything.
I had to recompile the 14.1 source code (32 bit) while actually using the current 32 bit Slackware.

I no longer get "Illegal command" failures when running import.

Thanks for pointing this out, I didn't note.
Recompiling imagemagick 6.9.0-10 (-current version) fixed the problem.

I have the same problem with Cups -current version (illegal instruction)
but recompiling doesn't work.

cwizardone · 05-30-2015, 07:37 PM

As previously mentioned,

Quote:

....finally took the same CD/DVDs that can be read and cannot be read in any of the 3 CD/DVD drives in this box and booted to winXp and then to PC-BSD 10.1. Both operating systems can read all the disks, without a problem in all 3 drives.
So... it has to be something to do with the mass upgrades of 21 April. What, I don't know.

Nothing has changed, in this regard, since 21 April. The problem remains.