First of all I want to say thanks for your time and explanations...
I'm going to try and re-explain my scenario, only because this thread has kind of bounced between two, kind of confusing them. And, to make it more complicated for me, it's on 4 lists. So here I go.
About a week ago I decided to move from spending most of my time
developing in php4 to beginning my transition to perl. I'm developing
a flash based content management system that's easier to use for novices.
Mostly I've stuck with a combo of Flash on the client (using actionscript 2.0,)
and PHP with MySQL on the back-end. It's been working beautiful, but
it only goes so far. We're going to need to automate account creation,
maintenance, etc... Right now we've been using propriety systems like
cpanel and modernbill. PHP is good, but doesn't do a lot of what we are
going to need. So enters Perl. It's that old saying, "I knew I'd be here someday;
I just didn't know yesterday, it would be today."
So I started writing and updater for our client sites. Then, I learned about the
benefits of mod_perl over mod_cgi and I was off. First thing I ran into was
a problematic DBD::mysql install. When I couldn't get it to install I tried a lot
of different approaches. That is when I think mod_perl got the databases
confused. I did eventually find the solution to get it to install here:
http://www.truerwords.net/3556
Alas, it was too late, I had a confused mod_perl. It was giving me the error
for a lib file that was for a database that was put in in one of my attempts
to get the DBD::mysql installed. It wasn't the database I really use.
To make things even more complicated it was a fink 'unstable' package,
I wouldn't even really want to use.
It was at this point that I found out a couple of other things.
First, I can only use $r->print( "something" ) to get output to the browser
when I use Apache::Registry a regular print doesn't do it, it does under
mod_cgi though. The second thing I figured out was when I ran DBD::mysql
under the perl command locally or as mod_cgi it connected to the right
database, just not under mod_perl using Apache::Registry.
Then I started to try and compile my own versions of Apache 1.3.33 (the same
as my production environment.) With or without fink or darwinports, by itself
or DSO with mod_perl, I can't get a successful apache 1.3.33 working.
I've gotten a lot of great suggestions, all of which I've tried, none have worked.
I'm not sure it's necessarily the only way to fix my problem though.
Starting to think like a perl guy (TMTOWTDI, right.) I'm guessing, not
sure but DBD::mysql or DBI is probably what set up mod_perl's lib. So, maybe
I just need to reinstall them. Otherwise, I can always back my user files
up and do a clean OS install (yuck!) I could keep trying to install my own
apache1.3.33 too. In fact, I'd like to be able to, regardless...
So as far as the dyld goes. Is it something that is only effected during source
compiling? If so I'd at least know it was one of the DB mods, for I haven't
compiled either apache or mod_perl successfully. So if dylds only get linked
during compile, using the env vars you explained, then I just need to reset
them, maybe taking my /sw/ directory out of $PATH while I compile, right?
Otherwise if there is a way to do it after it's compiled via editing a header
doc or something, maybe I just need to trackdown the file using a combo
of the grep commands you gave examples for in your last email, right?
Thanks again, Boysenberry
