As I'm currently having gcc-4.0.0 on the G/FBSD box, I'm having trouble with gcc-config script. The main changes in the patch I'm attaching are: - it doesn't use env -uCHOST as env -u doesn't work on, so saves, unsets and restores CHOST variable itself. - it checks for path for portageq as for other utils as the path problem is real on G/FBSD. - it uses ${CP}, ${TOUCH}, ${RM} and ${PORTAGEQ} instead of the direct command (see above). - it uses -pPR instead of -a on ${CP} as -a is gnuish thing. With those changes gcc-config works better, it just echo the warning * ./gcc-config: Profile does not exist or invalid setting for /etc/env.d/gcc/i686-unknown-freebsd5.3-4.0.0 but it works as it should anyway. HTH, Diego
Created attachment 57411 [details, diff] gcc-config.patch
cant we do something that isnt a hack to deal with the 'env -u' issue ? ive committed all the cp->$CP, rm->$RM, etc... changes in all the gcc-config versions and changed 'cp -a' to 'cp -pP' since that's all we needed
Uhm we can just use ${ENV} -i to give portageq an empty environment completely. That would be better?
that'd be fine actually, added to cvs
