SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
One more thing, have you tried the cvs snapshots of qemu ... maybe they got it working with the newer gcc ... they should have after all this time it has been out.
They won't... and that's for a while. The problem is that Qemu actually uses GCC to run ("it uses the compiler in some ways it wasn't meant to be used" http://lists.gnu.org/archive/html/qe...msg00238.html), mostly to generate the assembler-backend used to recompile code.
The thing is that there were some significant changes in the 4.x branch which had made it mostly uncompatible with the way Qemu uses it. Still, I've read of people who got it working with 4.0 (IIRC), but doing some odd tricks with the compiler (http://lists.gnu.org/archive/html/qe.../msg00187.html, that's for PPC, tho').
I didn't ask you to name them all. How about naming two?
How's about doing a little footwork yourself? Since you seem incapable of finding out for yourself I'll go ahead and tell you.
This is just from /var/log/packages and doesn't include symlinks. And this is also according to how I build it and not Slackware... Change my TARGET to Slackwares TARGET and that'll be about the only diff. And, ofcourse, I did a sed @opt/gcc-3.4.6@usr@ before my sort|uniq... As you can see, it will overwrite many files, thus resulting in a broken gcc-4. Do a uniq -u and you'll see all the broken clutter on your system doing nothing...
How's about doing a little footwork yourself? Since you seem incapable of finding out for yourself I'll go ahead and tell you.
Well, thank you for going to all that trouble. I did look for myself, actually, and didn't find any overwritten files that would affect how the gcc compiler works, except for the two I mentioned earlier. I forgot about documentation, and you're right, there are a lot of document files that would be replaced, as well as the bug-submitter and gcov. But the only other gcc file in the Slackware packages that might matter to how gcc compiles, so far as I can see, is /usr/lib/libgcc_s.so.1, and neither version of gcc is dynamically linked to that.
Why is this still being argued? It's a moot point. Eric has posted a link to gcc-3.4.6 packages on his page at Slackware.com; they solve the problem without any undesirable side effects.
It installs happily alongside the gcc4 that ships with Slackware-current, and it will not overwrite a thing. The compile of QEMU will pick up this gcc34 and build a good package. All the other software keeps compiling with the standard gcc4.
I have had several people reporting success in using this gcc34 package.
Read the SlackBuild for more information on how you can call the gcc34 binary if you need it.
Eric
Yay! Allright, Eric! I didn't see this when I browse through your 'site' before I'll try using your package first... lucky thing I haven't started compiling my own
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'll try using your package first... lucky thing I haven't started compiling my own 
