Good Morning and thanks for your help....here is an update
> > > Warning: Unable to load dynamic library
> > > '/usr/local/lib/php/extensions/no-debug-non-zts-20001222/midgard.so' -
> > > /usr/local/lib/php/extensions/no-debug-non-zts-20001222/midgard.so:
> > > undefined symbol: midgard_user_call_func in
> > > /usr/local/apache/libexec/midgard-root.php on line 12
>
> >> nm midgard.so |grep midgard_user should show you:
>
> >> 0000d920 T midgard_user_call_func
>
> and instead mine shows....
>
> U midgard_user_call_func
U -> undefined. So, thats it.
> which is why the module won't load right? So why, when I pull down a
clean
> tar, and removing all previous junk, am I getting the 3.0 library (which
> seems to be the root of problem)??
Martin was kind enough to reply again:
>>No. Got it (libmid..so.3) running under linux without problems.
>>So, like emile suggested, try the cvs snapshot. And after making every
>>packet have a look with ldd at the libs. there are so many dependencies
that
>>it is worse al look within the process, and not after all is finished.
>>Have a look with ldd at mod_midgard.
>>And some more information about System,php,apache are useful.
I went back to the beginning... I don't know if there was an issue with CVS
yesterday, my bad if I didn't say something, I was getting errors about the
directories not existing yesterday but I just tried a few minutes ago and
was able to get a good CVS update (phew)
I feel comfortable that things are getting back to normal....but there seems
to be an issue with mkall that probably started my huge mess. For
cleanliness, I install midgard into /usr/local/midgard....this didn't seem
to be a problem with the old mkall, as it worked as advertized, appending
the working directory passed as $ARGV[0] to the configure routine.
I'm in the middle of the mkall from the current CVS and the configure line
reads:
./configure --with-midgard
obviously there it is no longer taking a command line argument to change the
position of the install directory.
In the same light...there seems to be something wrong with the check for
midgard-config in both the configure scripts for mod and for php4 as
executing:
./configure (other command line args) --with-midgard=/usr/local/midgard
Does not result in the midgard-config file being found. A cursory glance at
the configure script looks like it is looking for midgard-config in the
ac_cv_path_MIDGARDCONFIG and not ac_cv_path_MIDGARDCONFIG/bin (where the
file is located)
It looks like the exact same code for checking for midgard-config has been
used in both the configure for mod and php4...so a bug in one would result
in the same problem for the other.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
