I mean *setup.py* ! ... (more questions)[Re: libraries=['m'] in config.py [Re: Python 2.1 alpha 1 released!]]

[Steven D. Majewski]

** I meant setup.py, not config.py! **


OK -- same sort of problem building readline.so :
 setup.py wants to include -ltermcap 

I was willing to write the other one off as a MacOSX oddity that
nobody on python-dev was likely to know about, but -ltermcap is
likely to be a problem on other systems too! 

So that makes me think I'm missing some obvious way of overriding 
these switches. Are there any docs or tips on this new setup 
method ?  Am I just supposed to edit the source of setup.py, or 
is it generated from some template ? 


-- Steve Majewski 



On Tue, 23 Jan 2001, Steven D. Majewski wrote:

> 
> 
> Is there a simple way (other than editing config.py) to remove the
> effect of all of the "libraries=['m']" options from config.py ? 
> 
> This breaks the MacOSX build as there's no libm -- that functionality
> is build into the System.framework .
> 
> Shouldn't these type of flags be acquired from configure or the
> make environment somehow ? 
>