Summary: | dev-lang/python - python-config emits local CFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Moritz Schlarb <moschlar> |
Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jer, moschlar |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Moritz Schlarb
2012-03-27 17:04:07 UTC
Created attachment 306875 [details]
build.log
emerge -pqv =sys-libs/tdb-1.2.7-r1
[ebuild R ] sys-libs/tdb-1.2.7-r1 USE="python -static-libs -tdbtest -tools"
The Internet says `-OPT:Olimit=0' is something the Intel C Compiler would use, and the sys-libs/tdb sources don't have anything like this string in them, so the conclusion would be that you compiled something with dev-lang/icc (instead of, say, sys-devel/gcc) and it then embedded its command line arguments somewhere in a configuration file that is used to compile python sources. Please post your `/usr/bin/python-config-2.7 --cflags' output in a comment. Mine seem to include my CFLAGS: -I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -O2 -march=k8 -ggdb -pipe -Wall -fwrapv -DNDEBUG so that's an error in dev-lang/python, not sys-libs/tdb. Hell yeah... mopad ~ # /usr/bin/python-config-2.7 --cflags -I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -OPT:Olimit=0 -march=prescott -O3 -pipe -fomit-frame-pointer -fwrapv -DNDEBUG But it wasn't icc's fault, since I experimented compiling Python with clang. So I either compile tdb with clang, too or I compile Python with gcc again. Anyway, I'm sorry for this bug... Since it is none! Thanks! |