Well, I made the "-rdynamic" change as follows, but I'm on thin ice here - I make no claims that this is correct and have no assurances that it "took": LDSHARED= @LDSHARED@ -rdynamic Anyway, it didn't help in my case. As I said, my problems now appear to be in Python. When I tried to build Zope, I would get overflow errors during the password generation. Then when someone suggested I run a Python "make test", I discovered that my Python installation was flawed. So, every since then, I've been trying to get Python built cleanly on my rented BSDI 3.0 box (a virtual server) without success. This isn't a problem on my Win9x systems, so I can still work with Zope and Python locally while I try to figure out the mysteries of BSDI (and virtual work spaces!). Pete -------- Pete Beazley - mailto:pete@clearlyonline.com ClearlyOnline, Inc. XML-based Web Applications - XML conversion - XML training http://www.clearlyonline.com 1-724-942-1912 1-724-941-3698 fax
Ah, no! I was cruising the list archives and saw your messages. I stupidly assumed from the fact that there was a FAQ relating to BSDI that there were a number of people running it using 3.0, but of course it doesn't *say* that <grin>.
I haven't had any problems with my Python. I didn't run a make test, but I didn't get any of those number related error messages you mentioned. I use Python extensively for sysadmin scripting, and it has been working fine (modulo a little popen hang problem I ran into in upgrading to 1.5.2). I don't think I tried to install 1.5.2 on a 3.0 system, though; all my boxes were at 4.0 before I started the upgrade from 1.4.
I *do* have Zope running fine on a FreeBSD 3.1 box. Compiled, installed, and ran with no problems. If it weren't that I'm afraid of breaking customer CGI scripts, I'd be tempted to just upgrade the BSDI box to FreeBSD.
So how did you make that -rdynamic change, and are you sure it actually "took" during the compile process?
--RDM