On Tue, Jan 10, 2006 at 09:53:36PM +0200, Jukka Heino wrote:
I can do a test run on current contrib ports to see how many fail when compiled with gcc 4.0.2. I'm okay with either bash 3.0 or a patched 3.1, but I recommend we stick with X.org 6.9 for now--it's essentially the same code base anyway.
I can say right now that xine-lib will fail, or not work properly (based on what I read, some months ago). Its 1.1.x branch is for GCC4, while its 1.0.x branch is for GCC3. What I wonder, is if most of ports/opt/ are like this; or if the latest versions do some autoconf check-GCC-version magic; or if we're going to have to pull in patches from the development branch of a particular port--or worse: be forced to use a development version. If an imminent switch won't cause a world of headaches, then I would advocate "let's give it a try, and see how it goes; if it works, then ship it ;-)". On the other hand, isn't the switch to GCC4 a HUGE leap? Shouldn't someone write some kind of migration document? (documentation seems like it has become an issue for some users) Something more substantial then: "after upgrading your system from the CRUX 2.2 iso, and rebooting, type: prt-get update -fr `prt-get listinst`" Out of curiousity, would prt-get rebuild the list alphabetically, or according to listed dependencies? Meh, forgive me for all this talk, when I know I won't be able to to much to help out (school). Nevertheless, I'll take care of xine-lib when the time comes. Cheers, Nick