Compiling Python 1.6 under MacOS X ...
Johann Hibschman
johann at physics.berkeley.edu
Sun Sep 24 04:53:09 EDT 2000
More information about the Python-list mailing list
Sun Sep 24 04:53:09 EDT 2000
- Previous message (by thread): os.chdir() considered harmful
- Next message (by thread): Compiling Python 1.6 under MacOS X ...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Peters writes: > So do all Windows filesystems, Python builds and runs fine on all flavors of > Windows, and has since '91. So, like I said, I have no idea what the new > problem may be with OSX. For every pair of distinct files X and Y in the > distribution, if X and Y are in the same directory, the names of X and Y > differ by more than just case. Or, if that's not true, it's a Unix(tm) bug > that doesn't affect Windows <wink>. Ah, but windows executables get ".exe" appended to them, while the unixy mac ones don't, so the executable conflicts with the diretory. I'm still trying to figure out how to get shared libraries to work, myself. I've got the static build of 1.5.2 at least to work, but no shared libs. --J -- Johann Hibschman johann at physics.berkeley.edu
- Previous message (by thread): os.chdir() considered harmful
- Next message (by thread): Compiling Python 1.6 under MacOS X ...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list