>Well, it's a change in some respects... Comment out mod_midgard again
>(but keep mod_php4 and midgard-php4), see if the segfault goes away.
>Midgard won't work, but at least it'd give me a handle on the
>segfault.
Ok...this is getting pretty frustrating...I realized that the bin, etc,
include, share directories were in /usr/local/ (i'm attempting to install in
/apps/midgard) from a previous installation, and i must have forgotten to
delete the midgard related files from there.   So, with all these seg faults
happening, i thought that maybe during the install, for some wierd reason it
was looking at those files instead, and when i actually tried to start
apache finally, it pointed to the wrong location, and voila! seg fault (all
my theories, which are known to be wrong).  With this in mind, i deleted
these files created from a previous install attempt (from
/usr/local/etc,bin...)  Now, the lib gets installed (creates bin, etc,
share...in /apps/midgard), and mod works also.  When in get to the
midgard-php step, i get:

checking for apxs... /usr/sbin/apxs
checking for midgard-config... no
configure: error: midgard-config not found. Did you install midgard-lib?
make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target `install'.  Stop.

This is odd...so i tried to manually copy the files over to the
/usr/local/directories.  This didn't work either...still couldn't find
midgard-config.  After this didn't work, i tried reinstalling it in
/usr/local/midgard, and same error...cold not find midgard-config.  SO...i
tried searching for midgard-config...and i couldn't find it!! I HAVE
installed midgard-lib...prefix=/usr/local/midgard.

Aditya.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to