On Wednesday 11 January 2006 03:41, Nick Steeves wrote:
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.
That's what I did. xine-lib: 1.1.0 (no problems with KDE, e17 and mplayer so far) http://crux.danm.de/ports/head/contrib64/xine-lib/Pkgfile xine-ui: 0.99.4 http://crux.danm.de/ports/head/contrib64/xine-ui/Pkgfile I had to tweak MPlayer a bit: --disable-gcc-checking (Gentoo made some nice patches for it: http://crux.danm.de/ports/head/compat32/mplayer32/mplayer-1.0_pre7-gcc4.patc... http://crux.danm.de/ports/head/compat32/mplayer32/mplayer-1.0_pre7-gcc4-amd6...) bye, danm -- Daniel Mueller Berlin, Germany OpenPGP: 1024D/E4F4383A