[ python-Bugs-1648957 ] HP-UX: _ctypes/libffi/src/ia64/ffi/__attribute__/native cc

SourceForge.net noreply at sourceforge.net
Wed Mar 7 10:05:29 CET 2007


Bugs item #1648957, was opened at 2007-01-31 10:07
Message generated for change (Comment added) made by cgaspar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1648957&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Abt (jabt)
Assigned to: Nobody/Anonymous (nobody)
Summary: HP-UX: _ctypes/libffi/src/ia64/ffi/__attribute__/native cc

Initial Comment:
_ctypes/libffi/src/ia64/ffi.c uses __attribute__((...)) twice. Consequently, ffi.c does not compile with the native compiler 
(cc: HP C/aC++ B3910B A.06.12 [Aug 17 2006]).


----------------------------------------------------------------------

Comment By: Carson Gaspar (cgaspar)
Date: 2007-03-07 04:05

Message:
Logged In: YES 
user_id=664506
Originator: NO

Fails on Solaris x86 10 U3 / Sun Studio 11 for the same reasons. It's
uncompilable on x86_64 anyway though, as Sun has no 128-bit integer type,
so the __int128_t in x86/ffi64.c will never compile. I haven't tried
building it in 32-bit mode.




----------------------------------------------------------------------

Comment By: Thomas Heller (theller)
Date: 2007-01-31 14:43

Message:
Logged In: YES 
user_id=11105
Originator: NO

I tried that on a HP testdrive machine.  While the _ctypes extension buils
fine with GCC (*), it does indeed not compile with the native C compiler.
But cc not understanding __attribute__ is only the first problem; if it is
removed there are lots of other compilation problems.  Unless someone can
provide a patch, I'll close this as 'won't fix'.

(*) _ctypes_test.so is also built but fails to load as shared library,
because the symbol __divsf3 is not defined.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1648957&group_id=5470


More information about the Python-bugs-list mailing list