I mean *setup.py* ! ... (more questions)

[Steven D. Majewski]

Thanks. I'll give the patch a try. 
I already hacked past that error by creating a fake libm.a file. 

The problem with the case insensitivity of Mac's HFS+ filesystem
has resurfaced in 2.1a1: 
 
 If termios, fcntl, etc. are built as shared modules, then importing
 TERMIOS, FCNTL, ... will cause a crash due to multiply defined symbols.
 ( It's importing the same shared lib twice, rather than getting the 
  .py file for the upper case module names. ) 


I was handling this in Setup by building those modules as built-in,
rather than shared. 

I see in the new Modules/Setup: 

# The modules listed here can't be built as shared libraries for
# various reasons; therefore they are listed here instead of in the
# normal order.


If there are modules in this list, does setup.py detect that and not
try to build them shared also ? 


-- Steve M. 


In article <3d3dea3vuh.fsf at ute.cnri.reston.va.us>,
Andrew Kuchling  <akuchlin at mems-exchange.org> wrote:
>
>setup.py was written using 2.0's Modules/Setup.in as a guide to
>platform specific problems; it didn't mention MacOS X, of course.  Try
>the untested patch below; you'll need to fix whatever sys.platform is
>on MacOS X.  Please let me know what it is and let me know if it
>works.
>
>Right now the only way to fiddle with setup.py is to edit it, and
>submit patches back.  I'm planning to have some command-line switches
>in the next alpha.
>
>--amk
>