[ python-Bugs-847812 ] 64 bit solaris versus /usr/local/lib

[SourceForge.net]

Bugs item #847812, was opened at 2003-11-23 15:25
Message generated for change (Comment added) made by benson_basis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=847812&group_id=5470

Category: Build
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: benson margulies (benson_basis)
Assigned to: Nobody/Anonymous (nobody)
Summary: 64 bit solaris versus /usr/local/lib

Initial Comment:
setup.py sticks /usr/local/lib in to the link path when 
building modules. On a 64-bit solaris machine, the 
libraries in there may well be 32-bit, and not work.

There needs to be some provision to control this, I think.


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

>Comment By: benson margulies (benson_basis)
Date: 2003-11-24 21:22

Message:
Logged In: YES 
user_id=876734

I knew there was something fundamental I was missing.

However, my copy of setup.py, which is not automatically 
generated, has /usr/local in it too, in 'detect_modules'. Or do 
those paths end up somewhere else.


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

Comment By: Martin v. Löwis (loewis)
Date: 2003-11-24 17:18

Message:
Logged In: YES 
user_id=21627

What kind of control are you thinking of? You *do* have
control over this at the moment: You can edit Modules/Setup,
and guide the build process explicitly what modules to pick
up from what location.

Some installations may have a /usr/local full of 64-bit
stuff, so I don't see a problem in this default.

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

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