Summary: | python 2.4 and icc inserts -OPT:Olimit flag to BASECFLAGS for distutils | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christopher Zapart <chris.zapart> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christopher Zapart
2005-11-05 05:06:16 UTC
http://sourceforge.net/tracker/?func=detail&aid=1162001&group_id=5470&atid=105470 seems like this problem, we probably should include this patch. did you compile python 2.4 with icc? yes, the python itself was compiled with icc. some of the various python utilities/extensions like pyopengl were compiled with gcc, the others, like pyode, compiled OK with icc. After reading your link from sourceforge I suppose the quick fix would be to recompile python with gcc and then try re-emerging pyopengl with gcc too. fortunately dev-python/visual, which is a real-time 3D graphics library for Python that I use most often, does not need pyopengl. thanks for your help, at least now it should be possible to use pyopengl by recompiling python with gcc. regards Chris An update: after recompiling pyopengl with icc (the same compiler as python itself was compiled) everything is working fine. The icc was indeed giving warnings about ignoring the option '-O' but it compiled OK. When a new x86 stable python came out a few weeks ago, pyopengl refused to compile with icc. therefore I tried using gcc only to get these '-OPT:0limit=0' errors. However, today pyopengl has compiled successfully with icc and I have verified it to work correctly too. So there is no need for recompiling python with gcc. I'm changing the status of the bug to "fixed". In the future I guess it would be good if patch for the -OPT setting could be included in the python ebuild. i think we should consider adding some sort of protection in case this happens. so i'm keeping this bug open. but thanks for your report back that things are back to normal. ICC is being phased out in portage. As I can't test ICC issues myself and ICC itself is being removed from portage I'm not going to do anything further now. Hopefully upstream can resolve any ICC related issues. |