This is basically what I did to get it working. I think the libraries being in a weird place stem from the --with-next-framework option which I assume expects to be put into an Openstep framework setup and set's Pythons paths to be:: .../lib/ instead of the usual:: .../lib/python1.5/ (the source says it's because NeXT's Frameworks do automatic versioning). This gets compiled _right into Python!_, but none of the makefiles and friends seem to catch it. My blue box STILL refuses to work (waaa!), so I spend a lot of time in either MacOS 8.6 or MacOS X Server (mostly in 8.6 due to (a) a better browser, and (b) more familier tools (yay Alpha!):)). Thus, I don't have access to that particular bit of patched Python source right now. It made things significantly easier, but was kindof a hack. I'd be very interested in getting more information about the NeXT Frameworks and maybe configuring the default Python makefiles to have a "make framework" option that basically acts like "make install", but takes into account any existing Python framework (like Objective Everything's for example) and follows the right versioning behaviour and other NeXT framework setups. That LDLIBRARY option not being included in Makefile.pre.in is rather a pain. -----Original Message----- From: Jim Washington [mailto:jwashin@mail.vt.edu] Sent: Monday, May 31, 1999 8:39 AM To: Greg Pierce; zope@zope.org Subject: Re: [Zope] Zope on Mac OS X Server Hi, Greg Yup. There was a note on the Python site from Jeffrey Shell with his solution. http://www.python.org/pipermail/pythonmac-sig/1999-May/001106.html I did something similar. Essentially: for Python: ./configure --with-next-framework --with-threads --with-dyld --prefix=[whatever] then put libpython1.5.dylib into /usr/lib No matter what you use for --prefix, this will put python and its development libraries in a really weird configuration that zope will not understand properly, so I symlinked the heck out of what I had to make it look like it was in "standard" locations. I suppose you could really move them around, too. adding LDLIBRARY=/usr/lib/libpython($VERSION).dylib into python's Makefile.pre.in in /lib/python1.5/config fixes the problems with finding the dylib change "sys.executable" to "[whatever]/bin/python" in wo_pcgi.py and do.py in your zope root. and I may have forgotten a thing or two, but it should compile and run. If you take better notes and get it working, you might post those to the list. I have a feeling OS X is going to be yet another popular platform for Zope. Now I need to try to get Mailman working... Good luck. --Jim Washington

i was wondering if anyone's gotten Zope running on Mac OS X server (theoretically, BSD 4.4 compliant). i already had built Python 1.5.2 and have been using it w/o incident. i downloaded the Zope 1.10.2 sources, and tried a build--which got pretty far along, but then failed on a number of counts and never created the config and launching files (the best i could tell).

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope (For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )