[ python-Bugs-1675511 ] Python still uses broken -xcode option on Solaris/x86

[SourceForge.net]

Bugs item #1675511, was opened at 2007-03-07 08:54
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1675511&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: Carson Gaspar (cgaspar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python still uses broken -xcode option on Solaris/x86

Initial Comment:
Bug 1561333 was submitted against Python 2.4 with no action, so I'm submitting a new bug against 2.5 in the hopes that someone will read it... text updated with minor corrections.

Python 2.5, Solaris x86 10 Update 3, Sun Studio 11

xcode=pic32 option is not supported on Solaris x86 Sun C  . Python's ./configure script on Solaris systems sets the
compiler flag -xcode=pic32 when any compiler other than gcc is used. Unfortunately, the -xcode flag is only available in the sparc version of Sun C. The x86 version of Sun C does not support the -xcode option at all and generates an error that an illegal option was used. The portable flag supported on both platforms to use independent 32-bit addressing is -KPIC.

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

>Comment By: Martin v. Löwis (loewis)
Date: 2007-03-10 18:07

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

Looks fine, although you might want to consider AMD64 as well. I think it
should be -KPIC (although I'm uncertain whether Python works on that system
at all). See

http://blogs.sun.com/x86be/category/Sun

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

Comment By: James Lick (jlick)
Date: 2007-03-10 17:14

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

I'm willing to take a stab at a patch.  I've reviewed the Sun Studio 11
documentation and it appears that the preferred options are:

Sun cc Sparc: -xcode=pic32
Sun cc X86: -Kpic

Does that match the way you read it, loewis?

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

Comment By: Martin v. Löwis (loewis)
Date: 2007-03-09 09:56

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

I don't want to make a change now, just to have to deal with a bug report
two years from now which then will sit again in this tracker for years
again. I'm fine with documenting that older SunPRO compilers are not
supported; -xcode has been supported atleast since Sun Forte 6 (released in
2000); earlier products had reached their end-of-life long ago. So either
this gets fixed properly now, or not at all.


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

Comment By: Carson Gaspar (cgaspar)
Date: 2007-03-09 09:06

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

While the doc labels the -KPIC option as "obsolete" for SPARC, it works
fine. Perhaps Studio 12 will break it, but all current compilers understand
it fine.

If you want to be pedantically correct and use -xcode=pic32, you don't
need an architecture test, you need to actually _try_ the option, as older
SPARC compilers won't accept it either.


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

Comment By: Martin v. Löwis (loewis)
Date: 2007-03-09 08:08

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

One problem is that the proposed change is incorrect. According to the C
User's Guide of Sun Studio 11 (document 819-3688-10), -KPIC is an obsolete
option on SPARC, and should be replaced with -xcode=pic32 (section
A.1.15).

So I think a patch should be architecture-specific. Can somebody come up
with a patch that does that?



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

Comment By: James Lick (jlick)
Date: 2007-03-07 09:34

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

Perhaps I was unclear in bug #1561333 that this resulted in only a
warning.  Actually the build will fail because of the incorrect flag.

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

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