Aditya Dhekney wrote:
> wow...hang on there...i don't know if that's exactly correct. if
> mod_midgard is enabled, php is completely taken out, apache starts.
OK. This is different from what we had before, right?
> Ofcourse because php is disabled, php isn't recognised (ie. <? phpinfo(); ?>
> gives <? phpinfo(); ?> as output). midgard-php4 doesn't come into the
> picture at all, since php.ini isn't read when php4 is commented out.
Right.
> Nontheless:
>
> ok...reinstalled from latest cvs. Just so you know everything, here is
> exactly what i did. There were a bunch of clock skew warnings during lib...
>
> [root@oddjob midgard]# ./bootstrap
>
> Bootstrapping lib
> automake: configure.in: installing `./install-sh'
> automake: configure.in: installing `./mkinstalldirs'
> automake: configure.in: installing `./missing'
>
> Bootstrapping mod
> configure.in:124: warning: Cannot check for file existence when cross
> compiling
So far so good.
> [root@oddjob midgard]# cd lib
> [root@oddjob lib]# ./configure --prefix=/apps/midgard
> --with-mysql=/apps/mysql
> --with-sitegroups --with-expat=/apps/expat
> creating cache ./config.cache
...
...
> creating midgard-config
> [root@oddjob lib]#make clean
>
> <bunch of output>
> this is interesting...at end have:
>
> make[1]: Leaving directory `/apps/midgard/midgard/lib/midgard'
> make: warning: Clock skew detected. Your build may be incomplete.
That's odd. Definately check that out. Make doesn't like time changes.
After a 'make clean', do a 'find . -type f -exec touch {} \;'.
> [root@oddjob lib]#make
>
> compilation output....again, interesting ending:
> make[1]: Leaving directory `/apps/midgard/midgard/lib'
> make[1]: Entering directory `/apps/midgard/midgard/lib'
> make[1]: *** Warning: File `midgard-config.in' has modification time in the
> futu
> re (2001-07-19 06:03:31 > 2001-07-18 20:12:50)
The touch will likely fix that. I've had this before on vmware systems
where the clock would be severly behind.
> [root@oddjob mod]# PATH=$PATH:/apps/midgard/bin
You may need to 'export PATH', or subshells won't see this. But if it
works...
> [root@oddjob php4]# PATH=$PATH:/usr/sbin
> [root@oddjob php4]# ./mkall /apps/midgard
> bunch of output...nothing abnormal
>
> ofcourse, when i say nothing abnormal, i mean no errors!
*grin*. I'm hoping "and then apache segfaults" doesn't become part of
"nothing abnormal". What's the scoop? So far the install looked OK.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
