Robert Dege <[EMAIL PROTECTED]> writes: > > Out of curiosity, what version of gcc-2.96 are/were you using? I have > > 2.96-98 here. > > > > I've built mplayer with gcc-2.96 on several different machines without > > difficulty. (i586, i686, and athalon) I put together a spec file and a > > patch for their configure script to build my own rpms for mplayer-0.50 > > and 0.60 as well. If your interested in trying them (the spec and the > > patch, binaries are not distributable), they are here: > > http://www.tuxfan.homeip.net:8080/rpms/mplayer/ > > Additionally, you'll need to grab the source from the developers site. > > At first, I tried using the stock rpm that came with the distro. but > during compiling, I kept getting some sort of %slx errors that was > crashing the compile. So I went to the update portion of Redhat's site > & upgraded to the latest version of 2.96 (not sure what that was). > Still, no change.
No, this is(was?) a bug in mplayer, not in the compiler. More details at http://www.bero.org/gcc296.html > I then upgraded to 3.1 (which caused nothing but > nightmares there on in). Not only did MPlayer not compile, but other > programs that did compile correctly, caused unknown seg faults, and > other various disturbances. But I chalked that up to beta releases. Yes. It's not binary compatible with the old one either, so it will break. > So as a last resort, I downgraded to 2.95. I haven't had a problem > since. It's not binary compatible with gcc296 (or other versions) wrt. C++. It also has worse performance, more bugs and poorer C++ conformance (and of course, doesn't run at at all on IA64) -- Trond Eivind Glomsrød Red Hat, Inc. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
