install gcc-3.4.6 in slackware-current

Alien Bob · 05-29-2007, 01:17 PM

No they haven't. And I doubt they will anytime soon.

Eric

theoffset · 05-29-2007, 02:04 PM

Quote:

Originally Posted by H_TeXMeX_H

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').

H_TeXMeX_H · 05-29-2007, 03:02 PM

Oh, I see, didn't know that. Thanks for the info. Guess the only solution is to install gcc-3.x. Oh well ...

jong357 · 05-29-2007, 03:36 PM

Quote:

Originally Posted by GregLee

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...

Code:

$ cat gcc-4.2.0-i686-1 gcc-3.4.6-i686-1 | sort | uniq -d
usr/bin/c++
usr/bin/cpp
usr/bin/g++
usr/bin/gcc
usr/bin/gccbug
usr/bin/gcov
usr/bin/i686-pc-linux-gnu-c++
usr/bin/i686-pc-linux-gnu-g++
usr/bin/i686-pc-linux-gnu-gcc
usr/info/
usr/info/cpp.info
usr/info/cppinternals.info
usr/info/gcc.info
usr/info/gccinstall.info
usr/info/gccint.info
usr/lib/libgcc_s.so.1
usr/lib/libstdc++.a
usr/lib/libstdc++.la
usr/lib/libsupc++.a
usr/lib/libsupc++.la
usr/man/
usr/man/man1/
usr/man/man1/cpp.1.gz
usr/man/man1/g++.1.gz
usr/man/man1/gcc.1.gz
usr/man/man1/gcov.1.gz
usr/man/man7/
usr/man/man7/fsf-funding.7.gz
usr/man/man7/gfdl.7.gz
usr/man/man7/gpl.7.gz
usr/share/
usr/share/locale/
usr/share/locale/be/
usr/share/locale/be/LC_MESSAGES/
usr/share/locale/be/LC_MESSAGES/gcc.mo
usr/share/locale/ca/
usr/share/locale/ca/LC_MESSAGES/
usr/share/locale/ca/LC_MESSAGES/gcc.mo
usr/share/locale/da/
usr/share/locale/da/LC_MESSAGES/
usr/share/locale/da/LC_MESSAGES/gcc.mo
usr/share/locale/de/
usr/share/locale/de/LC_MESSAGES/
usr/share/locale/de/LC_MESSAGES/gcc.mo
usr/share/locale/de/LC_MESSAGES/libstdc++.mo
usr/share/locale/el/
usr/share/locale/el/LC_MESSAGES/
usr/share/locale/el/LC_MESSAGES/gcc.mo
usr/share/locale/es/
usr/share/locale/es/LC_MESSAGES/
usr/share/locale/es/LC_MESSAGES/gcc.mo
usr/share/locale/fr/
usr/share/locale/fr/LC_MESSAGES/
usr/share/locale/fr/LC_MESSAGES/gcc.mo
usr/share/locale/fr/LC_MESSAGES/libstdc++.mo
usr/share/locale/ja/
usr/share/locale/ja/LC_MESSAGES/
usr/share/locale/ja/LC_MESSAGES/gcc.mo
usr/share/locale/nl/
usr/share/locale/nl/LC_MESSAGES/
usr/share/locale/nl/LC_MESSAGES/gcc.mo
usr/share/locale/rw/
usr/share/locale/rw/LC_MESSAGES/
usr/share/locale/rw/LC_MESSAGES/gcc.mo
usr/share/locale/sv/
usr/share/locale/sv/LC_MESSAGES/
usr/share/locale/sv/LC_MESSAGES/gcc.mo
usr/share/locale/tr/
usr/share/locale/tr/LC_MESSAGES/
usr/share/locale/tr/LC_MESSAGES/gcc.mo

GregLee · 05-29-2007, 05:23 PM

Quote:

Originally Posted by jong357

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.

rworkman · 05-29-2007, 07:06 PM

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.

lordwolf · 05-30-2007, 01:19 AM

Quote:

Originally Posted by Alien Bob

Alternatively you can install my gcc34 "compatibility" package from here: http://www.slackware.com/~alien/slackbuilds/gcc34/

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