OK, a few packages break with LIBC set in the environment. Known problems at the moment are python (workaround already in), csh, and openoffice. I'm creating this bug to track packages that need modification, and if there turn out to be too many of them we can find a more centralised solution, possibly renaming the variable. CC-ing taviso as he seems to maintain csh -- I have a fix for it; let me know whether I can commit it, or if you want to do it yourself.
*** Bug 91155 has been marked as a duplicate of this bug. ***
For OOo, there seem to be multiple configure scripts, called indirectly, so adding 'unset LIBC' at the beginning of src_compile seems to be the simplest way forwards, unless one of the openoffice team can come up with a way of passing --with-lib='' to all of them.
Urm, that's --with-libc='' in comment #2.
Hi all, OOo 1.1.4 was breaking for me, and using: --with-libc='' as an argument to configure didn't fix it. Stephen then suggested adding: unset LIBC directly to the "src_compile" function method of the ebuild, and that worked. OOo 1.1.4 compiled successfully and is now installed (and works). :) The exact change made was: *********** src_compile() { addpredict /bin addpredict /root/.gconfd export MYCONF="" *********** to: *********** src_compile() { unset LIBC addpredict /bin addpredict /root/.gconfd export MYCONF="" ***********
Fix is no in the tree for all versions of openoffice and openoffice-ximian, thanks for reporting (and solving)
OK, LIBC got renamed to ELIBC, so this can be ignored now.
@Stephen: Does that also mean that I can safely remove the "unset LIBC" line again?
Should be safe, but I'd check to make sure before committing anything.
*** Bug 93175 has been marked as a duplicate of this bug. ***
