[Python-bugs-list] [ python-Bugs-629345 ] build does not respect --prefix

[noreply@sourceforge.net]

Bugs item #629345, was opened at 2002-10-27 07:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=629345&group_id=5470

Category: Build
Group: Python 2.1.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Philip Brown (theferret)
Assigned to: Nobody/Anonymous (nobody)
Summary: build does not respect --prefix

Initial Comment:
I want to compile python with a different prefix.
I use configure --prefix=/my/stuf

but some things are still hardcoded to look in /usr/local

for example, setup.py

This stops extensions like bsddb from being built, even
though the include files are present in $prefix/include

Even if I go the extra mile to do export
CPPFLAGS=/my/stuff,
and the configure script successfully detects I have
db.h... 
it STILL does not compile bsddb until I make a link from
/my/stuff/include/db.h to /usr/local/include/db.h


Please fix all those locations that have hardcodes for
/usr/local




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

>Comment By: Philip Brown (theferret)
Date: 2002-10-27 19:27

Message:
Logged In: YES 
user_id=7120

When trying to detect whether a library is available, you
should at least respect LD_LIBRARY_PATH  if it is set,
rather than hardcoding stuff like /usr/local reguardless of
$prefix





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

Comment By: Martin v. Löwis (loewis)
Date: 2002-10-27 18:54

Message:
Logged In: YES 
user_id=21627

#--prefix specifies what to put in strings instead of
/usr/local.

No. See ./configure --help:

  --prefix=PREFIX         install architecture-independent
files in PREFIX
                          [/usr/local]


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

Comment By: Philip Brown (theferret)
Date: 2002-10-27 18:51

Message:
Logged In: YES 
user_id=7120

--prefix specifies what to put in strings instead of
/usr/local. It is common practice to install ALL free
software under a /usr/local equivalent. eg: /opt/freeware

Clearly, /opt/freeware is for ALL freeware, not just for
"this package".
It is the most consistent to scan whatever was specified for
$prefix, rather than to hardcode for /usr/local

Additionally, there could conceptually be other stuff in
/usr/local that might conflict (which actually happend to me)

The whole point of --prefix is to specify a location to use
INSTEAD OF /usr/local. If the user/admin explicitly says "do
not use /usr/local, use this path instead", you should NOT
use /usr/local !!

(unless it is in $PATH, $CPPFLAGS, or $LD_LIBRARY_PATH.
Which it is not, in my case)




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

Comment By: Martin v. Löwis (loewis)
Date: 2002-10-27 12:20

Message:
Logged In: YES 
user_id=21627

This is by design.

--prefix specifies the places to install *this* package
(i.e. python), not the places to look for other packages.

If you want to find libraries in different locations, edit
Modules/Setup appropriately; setup.py is not designed that case.

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

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