April 1999 - Zope - Zope lists

Building Zope on BSDI
by John Eikenberry 01 Apr '99

01 Apr '99

Has anyone built Zope on a BSDI machine? BSDI doesn't support shared libraries, so everything has to be statically compiled into python. I just got it to build (python w_pcgi.py finished), but there doesn't seem to be a new python binary anywhere with everything compiled in. To get it to compile, I went through and deleted all the '*shared*' from the 'Setup' files. Any tips? As a side note, I was planning on using the binary porting kit to get it built, then contributing this back to the community. But the porting kit is still Zope-1.9. Is there any plans to update the porting kit. Thanks in advance for any help, --- John Eikenberry [jae(a)kavi.com - http://taos.kavi.com/~jae/] ______________________________________________________________ "A society that will trade a little liberty for a little order will deserve neither and lose both." --B. Franklin

3 3

Building dtml objects now...
by andreww＠netscape.com 01 Apr '99

01 Apr '99

Im finally starting to build some DTML objects for Dreamweaver, and I wondered if folks could tell me what their "wish - list" might be for this. For example for the VAR tag, do you really want to have to specify all those attributes or should there be a secondary simpler object that just inserts a  Someday when/if dreamweaver get's webdav savvy Ill have the var object obtain a list of all available variables at that level and allow you to just "choose" one. The possibilites are there. -- ------------------------------------------------------------------------- - Andrew Wooldridge - Opinions expressed are my own - - andreww(a)netscape.com - http://people.netscape.com/andreww/ - ICQ: 6345881 - Find It at http://dmoz.org - -------------------------------------------------------------------------

1 0

RE: [Zope] Building Zope on BSDI
by Brian Lloyd 01 Apr '99

01 Apr '99

> > > Has anyone built Zope on a BSDI machine? BSDI doesn't > support shared > > > libraries, so everything has to be statically compiled > into python. > > > I just got it to build (python w_pcgi.py finished), but > there doesn't seem > > > to be a new python binary anywhere with everything > compiled in. To get it > > > to compile, I went through and deleted all the '*shared*' > from the 'Setup' > > > files. Any tips? <snip> > > So... any tips for compiling the Zope extensions as shared libs? I'll > probably keep working on the static python solution, as I'm actually > making progress on this, and I really have no idea where to start with > shared libs on BSDI (no good leads on dejanews, and egroups is > non-responsive as usual). > > Thanks, > > --- > > John Eikenberry Here are some things I've found in previous struggles to get Zope compiled on bsdish systems -- I'm no guru, though, and I've seen different things work on different bsdx flavors: o you usually need to add -rdynamic to LDSHARED in your Makefiles (this should be reported & worked into python's makefiles, IMHO) o I havent been able to get threads going on many bsd flavors - so you may not be able to pass --with-thread to configure o I find that extensions will all appear to blow up with unfound symbols (such as those you reported) - you need to run make -k and ignore the errors ;) o On some systems, I had to run make -k, ignore the errors, and rename the output .o files for the extensions to .so :( o I seem to remember having to use shlicc on .so files, but I dont recall the details... Hope this helps - please post a status rpt if you get it working, so that the gory details will at least be captured. This is the sort of thing that should be in an installation FAQ somewhere. Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

2 1