Summary: | /dev-lisp/clisp-2.43-r1 : error: `CPPFLAGS' has changed during compilation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sasha Medvedev <Sasha.Medvedev> |
Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sasha Medvedev
2008-04-24 19:31:34 UTC
not sure what's going on, but you could give the ebuild from bug 218739 a try Ebuild from bug 218739 give the same result. I've tried to remove i18n module from ebuild and have the same error. Please unset $CPPFLAGS and retry the compilation. The contents of your $CPPFLAGS are erroneous, because those are flags valid for the compiler, not for the preprocessor. I unset $CPPFLAGS and compilation works for me now. So, should I change bug status to INVALID? Is this my mistake or ebuild? May be somebody explain me why this flags are invalid or somebody give me a link. If you read the cpp(1) manpage you'll see that none of the flags you have in $CPPFLAGS are valid for the preprocessor. The only reason why you've never noticed this problem is that almost all programs don't separate preprocessing from compilation and just pass those flags to gcc. The solution is not to even set $CPPFLAGS unless you know well what you're doing. Thanks! |