Mark Lawrence added the comment:
Can we close this as I cannot see how a test failure against a 6.5 year old
alpha build can still be relevant?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
Changes by Gregory P. Smith g...@krypto.org:
--
resolution: - out of date
status: languishing - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
___
Python-bugs-list
Mark Lawrence added the comment:
Given the title is this still relevant given that Oracle Solaris 11 is closed
source?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
Changes by Christian Heimes li...@cheimes.de:
--
status: open - languishing
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 2.7 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
___
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
___
Python-bugs-list
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2552
___
___
Python-bugs-list mailing list
Martin v. Löwis [EMAIL PROTECTED] added the comment:
If option --with-system-ffi is not specified and if the compiler is not
gcc, raise an error.
Up to here, it all sounded fine. What do you mean by error? Abort?
That should not happen. Instead, setup.py skips modules if it doesn't
find the
Jean Brouwers [EMAIL PROTECTED] added the comment:
Agreed. In addition, gcc -v writes to stderr and catching the output
requires redirecting stderr or using os.popen3 or -4. The latter fail
since the select module (needed by subprocess) is still missing at that
time.
Going back to Thomas'
Jean Brouwers [EMAIL PROTECTED] added the comment:
Instead of ... raise an error, it should read ... report the _ctypes
module as missing, do not run any tests, etc.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2552
Jean Brouwers [EMAIL PROTECTED] added the comment:
Yes, but the _ctypes module requires gcc, as Thomas Heller mentioned. The
only thing which can be done is avoid building the _ctypes module if the
compiler is not gcc. I did look at fixing that but have not found the
proper way to do that.
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Yes, but the _ctypes module requires gcc, as Thomas Heller mentioned.
So the proper fix for that would be to port it to SunPro, of course.
The
only thing which can be done is avoid building the _ctypes module if the
compiler is not
Jean Brouwers [EMAIL PROTECTED] added the comment:
For ctypes to compile with the SUN's C compiler, there is quite a bit of
tricky asm code which needs to be ported (and tested). Most of that is
in libffi and that library is only supported with gcc, it seems. But
that is not mentioned
Jean Brouwers [EMAIL PROTECTED] added the comment:
The setup.py module contains method detect_ctypes on line 1546 which
handles the ctypes module building and testing. Would it be OK to not
do any of that on Solaris, if the compiler is not gcc?
Also, SUN Studio 12, the latest edition of
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Would it be OK to not
do any of that on Solaris, if the compiler is not gcc?
That would be fine.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2552
__
Jean Brouwers [EMAIL PROTECTED] added the comment:
Attached is one attempt to avoid building the _ctypes module if the
compiler is not gcc: a patch for Python 2.6a2 with just 2 changes for
setup.py based on the value of config variable CC.
--
keywords: +patch
Added file:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I think this is incorrect; CC might also be gcc -pipe or
/usr/local/bin/gcc, or some such, and would still be gcc (perhaps even
/usr/local/bin/cc).
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2552
Thomas Heller [EMAIL PROTECTED] added the comment:
I'm curious: Why do you insist on using the sun compiler? Are there
political or technical reasons?
Another thing: in principle it should be possible to build a libffi
shared library with gcc, and use it in a sun-c compiled python build.
At
Gregory P. Smith [EMAIL PROTECTED] added the comment:
agreed, do not check to see if the string is == 'gcc'. Instead,
actually execute the CC compiler with a -v flag and test if 'gcc
version' in output.
something like this (but split into a few statements for readability):
if 'gcc version'
Jean Brouwers [EMAIL PROTECTED] added the comment:
Well, so much for the first attempt. I'll see what it takes to use
something else, like ac_compiler_gnu. Unless Gregory's suggestion
qualifies.
Also, I am using SUN's compilers on Solaris 10 for 'political' and some
technical reasons. And
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Well, so much for the first attempt. I'll see what it takes to use
something else, like ac_compiler_gnu. Unless Gregory's suggestion
qualifies.
I would prefer to see the configure test for gcc be recorded and
passed through, over
New submission from Jean Brouwers [EMAIL PROTECTED]:
The ctypes test failed since the _ctypes module did not compile for 32-
bit Python 2.6a2 on Solaris 10 (Opteron) built with the SUN C compiler.
...
cc -KPIC -xtarget=native -DNDEBUG -xO5 -I. -I/.../tools/Python-
2.6a2/./Include
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Are you interested in working on a patch?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2552
__
24 matches
Mail list logo
