do we Leave Slackware 13.37 broken for Me ?
 

You know the uprade in patches been there a long time. don't do it the glibc build broke most of the art work. In many of my builds I develop. well and the same for the multilib. I was wondering why my friends started saying my builds didn't work.

And why my builds would start and not render correct then freeze well I went back and reinstalled the old ones fixed.
mmm
for the multi lib I had to recompile them as per Alien bob's wonderful documents.
So now should I call slackware broken? No not broken one man fix may break a lot
.BUT!.
to have it so long and so stable Pat I only hope the gtk2 and the glibc get back in sync some time.
I always use everything from slackbuilds or from Pats builds. only ones I don't are a couple and it is the Makepkg script in the slackbuild script that has caused permissions problems or wrong links. So what easy stuff to handle
but they still get added to slackbuild every year, Not complaining my check will be in the mail for slackware14 that impossible gcc 4.7 is killing ME. . but the glibc is broken for me in slack13.37 it will compile it will run fine but that art work is not working. :)
So no one takes this wrong these are experimental builds and most of the problems are on my side OK Slackware Fans :)

I gather you're not asking a question, but venting.

It would be more productive to include the relevant errors, and when the issues are clear, one of 2 things will show.
1. Actually, the system wasn't set up right
2. Actually the updates were broken.

Either way the world of slackware will be better off. This way,(hiding the errors), you just get ignored as a crank.

I have no idea of what you are talking about Drakeo.
Please explain your issues, give examples, error messages, etc, so that we can try giving reasonable answers... or else you better stay away from the alcohol.

Eric

Your english is horrible man.

James Joyce on acid?

For now, unfortunately, no-one can understand what you're saying.

Posting screenshots might help us understand what you're going through.

Nothing like a good sense of humor
 

I laughed out loud when i read this one...thanks Eric

I loved James Joyce on acid too...made my day guys

Busby

I studied Literature and Classical Philology back in the early nineties, so I basically know how to approach, say, a prose poem by Stéphane Mallarmé, some of the more hermetic works from Paul Valéry, or one of Marcel Proust's three-page-convolutions. I don't shy away from Hölderlin's, Rilke's or Wallace Stevens' more obscure poem collections.

But this posting. Wow.

Drakeo, when building projects always check compile flags and the options for GNU-Make and make sure you use optimizations that are universal to the platform. If you are using x86_64 or iX86 make sure you use make options

and build for platform architecture:

If you build a software package on an Intel platform and it optimizes it for something like SSE3 and you try running it on an AMD system, it might not run at all because SSE3 might not be on that processor. Nocona w/o SSE3 and i486 are probably the most universal architecture types.

However, when you build projects, as stated, check and see what the build options are, or distribute a buildscript and let them build the project on their own workstations.

sorry for not getting back yay Old old open it was ME not them . well a little them LOL. actually when installing it it changed some config files that did not work with the programs . I will never give up on Slackware 13.37 my favorite so far and 14 will grow on me. And create more work. So why does the update bork the alsa hardware config . you see if the program did not find the default sound card it crashed (actually freeze loading the artwork openjpeg 1.4 the program. anyway life and learning and KISS.
want to thank you all for your replies very sorry for not getting back faster.
Thanks pat for the Slack 14 and yes sent my funds.

The question should read why when installing the the updated gcc why did it change the hardware configs a manual /etc/modprobe.d/sound.conf has fixed it. why when before regressing to the old one did it fix it. well I tested it and am back to the latest patches and in sync for many more upgrades.
not going to uninstall and reinstall again to test it. it is working fine.

well thank you for the kind reply I wish you a wonderful day sir. working dyslexia has been a problem for me for many years so I am so glad I found you to help me.
Living in the visual world is a way of life love and be loved.

well sober doesn't help much either Eric but thank you for your hard work sir. and the art of building the ffmpeg.

everyone deserves a good laugh

thank you for your kind reply yes I made sure it was not a compiling problem it was a configuration problem KDE not setting default hardware and that was needed.

---------- Post added 10-04-12 at 10:38 AM ----------

wow sounds like great art history.

thats not new and I am used to it please read above. thank you for being kind to a old man.