[issue6138] './configure; make install' fails in setup.py step if .pydistutils.cfg specifies 'home'

[Ned Deily]

Ned Deily added the comment:

Let's consolidate these.

--
nosy: +ned.deily
resolution:  -> duplicate
stage:  -> committed/rejected
status: open -> closed
superseder:  -> during Python installation, setup.py should not use 
.pydistutils.cfg

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6138] './configure; make install' fails in setup.py step if .pydistutils.cfg specifies 'home'

[Éric Araujo]

Éric Araujo  added the comment:

See #4655.  (Not sure which one is the superseder.)

--
nosy: +eric.araujo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6138] './configure; make install' fails in setup.py step if .pydistutils.cfg specifies 'home'

[R. David Murray]

R. David Murray  added the comment:

I figured it out.  It turns out that a while back I created a
.pydistutils.cfg file and put home in there.

There is a bug here, of some sort.  Either the .pydistutils.cfg file's
install clause should override the default --prefix somehow, or the
error message should indicate where the setting for 'home' and
'--prefix' came from to enable the user to debug the configuration.  In
the latter case there would also need to be a way to explicitly tell
either make install or configure to ignore .pydistutils.cfg.  In the
former case, an explicit --prefix passed to configure would need to
override .pydistutils.cfg.

Or perhaps there's some other solution I'm not seeing at the moment.

--
title: ./configure; make install fails in setup.py step -> './configure; make 
install' fails in setup.py step if .pydistutils.cfg specifies 'home'

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com