This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: readline module doesn't build on MacOSX
Type: Stage:
Components: Build Versions: Python 2.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: brett.cannon Nosy List: brett.cannon, skip.montanaro
Priority: normal Keywords:

Created on 2004-12-08 02:19 by skip.montanaro, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
setup_fix.diff brett.cannon, 2004-12-18 07:56 Use distutils.sysconfig.get_config_var() instead of sys.getenv()
Messages (6)
msg23604 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2004-12-08 02:19
Recent changes to either configure or setup.py seem to
have conspired to prevent the readline module from
building on MacOSX.  I configured and built with

    LDFLAGS='-L/sw/lib' CPPFLAGS='-I/sw/include' ../
configure '--prefix=/Users/skip/local'
    make

The relevant readline bits are in /sw/... but the
module is not built.  The following bits containing
/sw grep out of the generated Makefile:

    INSTALL=        /sw/bin/install -c
    CPPFLAGS=       -I. -I$(srcdir)/Include -I/sw/include
    LDFLAGS=        -L/sw/lib
    CONFIG_ARGS=    '--prefix=/Users/skip/local' 
'CPPFLAGS=-I/sw/include' 'LDFLAGS=-L/sw/lib'

Assigning to Brett since he touched this most recently.

Skip
msg23605 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2004-12-08 02:46
Logged In: YES 
user_id=44345

More on this...  Sticking a print of lib_dirs just before setup.py
checks for readline shows that /sw/lib is not in that list.
msg23606 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2004-12-10 19:44
Logged In: YES 
user_id=357491

I have uploaded a patch to add some debugging output.  Can you run 
make and let me know what it outputs (might need to touch a file to 
trigger the need for setup.py to execute)?  I need to know exactly what 
the environment variables are set to when they are parsed and what 
setup.py ends up with for its library and include directories.
msg23607 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2004-12-18 07:56
Logged In: YES 
user_id=357491

I was able to reproduce the problem of the environment variable 
returning None for a short time (it for some reason stopped doing that 
and started to do what I expected).  While I could, though, I was able to 
get the right values using distutils.sysconfig.get_config_var().

The attached file adds a little bit more debugging output and also 
switches over to using distutils.sysconfig.get_config_var() instead of 
sys.getenv().  Let me know if that fixes the problem.
msg23608 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2004-12-18 19:59
Logged In: YES 
user_id=44345

That worked...  Thanks... (check it in?)
msg23609 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2004-12-18 20:48
Logged In: YES 
user_id=357491

Checked in under rev. 1.209 in setup.py .
History
Date User Action Args
2022-04-11 14:56:08adminsetgithub: 41297
2004-12-08 02:19:03skip.montanarocreate