The what should be updated in -current thread

Which does not change the point that stuff that used to compile now fails without patching.

Originally Posted by allend Which does not change the point that stuff that used to compile now fails without patching.

ok, you are cool because you can say "latest is not always the greatest"
shall we also start patching makefile and write the SLKCFLAGS into them?

remove double post

GCC-4.9.2 needs time to get ironed out. Because it's a compiler and an essential part of the system, it needs to be thoroughly tested. In honesty, if 4.8.x works, and still works and anything can't be built by LLVM/Clang, we're good with 4.8.x until 4.9.2 can get a proper shakedown.

Originally Posted by ReaperX7 GCC-4.9.2 needs time to get ironed out. Because it's a compiler and an essential part of the system, it needs to be thoroughly tested. In honesty, if 4.8.x works, and still works and anything can't be built by LLVM/Clang, we're good with 4.8.x until 4.9.2 can get a proper shakedown.

you mean gcc-4.9.2 needs more time to harden than gcc-4.7.1 or gcc-4.8.2 needed?
aha
guys I appreciate your enthusiasm and the will to answer my question,
but speculations, opinions and nonsense, like the 2 answers I got, are not a help.
I ask for technical and/or real reason like, this or that does not compile, this or that bug, PV had not time, ...

Originally Posted by a4z you mean gcc-4.9.2 needs more time to harden than gcc-4.7.1 or gcc-4.8.2 needed? aha guys I appreciate your enthusiasm and the will to answer my question, but speculations, opinions and nonsense, like the 2 answers I got, are not a help. I ask for technical and/or real reason like, this or that does not compile, this or that bug, PV had not time, ...

gcc 4.8 series has been in current for a while now
it was added to current on "Fri May 9 01:47:42 UTC 2014"
same day is when the kernel got upgraded to 3.14

if you followed the changelog, you would note that slackware is upgraded bottom up
not at random
this way is better in the long run, as bugs due to gcc get discovered early instead of on release

Originally Posted by genss gcc 4.8 series has been in current for a while now it was added to current on "Fri May 9 01:47:42 UTC 2014" same day is when the kernel got upgraded to 3.14 if you followed the changelog, you would note that slackware is upgraded bottom up not at random this way is better in the long run, as bugs due to gcc get discovered early instead of on release

aha, and when do you change do a new compiler following your way? short after a release you change one in current and than that's it until the next release?
btw, if following you expert expertise that gcc was added on "Fri May 9 01:47:42 UTC 2014" to current
how is is possible that Slackwaer 14.1 comes with gcc 4.8.2
but thanks for your enthusiasm to answer, nice that you tried a guess

Originally Posted by a4z aha, and when do you change do a new compiler following your way? short after a release you change one in current and than that's it until the next release? btw, if following you expert expertise that gcc was added on "Fri May 9 01:47:42 UTC 2014" to current how is is possible that Slackwaer 14.1 comes with gcc 4.8.2 but thanks for your enthusiasm to answer, nice that you tried a guess

14.1 got gcc 4.8.0 on "Wed Mar 27 06:09:29 UTC 2013"
that's 4 months after 14.0 was released and bit over 7 months before 14.1 was released

gcc 4.9 was released on "22 April 2014", so almost 5 months after slackware 14.1


PS 4.9 does not bring much performance wise
also; i think Pat looks more on open bugs then dates

Originally Posted by genss 14.1 got gcc 4.8.0 on "Wed Mar 27 06:09:29 UTC 2013"

Slackware 14.1 comes with gcc 4.8.2

Originally Posted by genss gcc 4.8 series has been in current for a while now it was added to current on "Fri May 9 01:47:42 UTC 2014"

Please note that the changelog says "rebuilt"... not "upgraded"...

Originally Posted by Slax-Dude Slackware 14.1 comes with gcc 4.8.2 Please note that the changelog says "rebuilt"... not "upgraded"...

hence the "got"

yes, i knew but wrote anyway

Originally Posted by genss sox has a new maintenance release

Got it; thanks!

Originally Posted by ReaperX7 xfce4-mixer may need a small replacement. What about replacing it with volumeicon from sbo? We could import it or alsamixergui for an xfce4-mixer replacement that's minimal and easy to use.

xfce4-mixer is just fine for now as long as you do have gstreamer-0.10.x installed and you don't have PulseAudio installed. If you do have PA installed, then there's a separate panel plugin for that (xfce4-pulseaudio-plugin) that's under active development.

From trying out volumeicon, all it does is open a console to alsamixer, which oddly is the default volume controls. It does work with any desktop provided you set it up in the startup and session management. It's minimal but nice, but PulseAudio isn't an option.

If gstreamer-0.x still works under Xfce 4.12 then we should be okay, but the project may start showing age eventually.

I'm now using oss so I have the ossxmix utility.

The good part is Robby, we have options.

Yeah, there are options. mate-media, which requires mate-desktop and libmatemixer, is quite nice.

Could I suggest upgrade of libtiff from 3.9.7 to 4.0.3 please? I found that version 4.0.3 was necessary to build OpenImageIO-1.5.2 (or 1.6.1dev). It (libtiff-4.0.3) was released Sept. 2012 so could be regarded as stable by now and there's a 4.0.4beta (Jan. 2015) out there too.

chris