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

[M.-A. Lemburg]

"Steven D. Majewski" wrote:
> 
> ** 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 ?

Please post these suggestions on the Python bugs listm, Python-Dev
or Andrew Kuchling who wrote the setup.py script -- the
distutils approach to auto-configuring Python's builtin modules
is very new and still needs some refinements.
 
> -- 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 ?
> >

-- 
Marc-Andre Lemburg
______________________________________________________________________
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/