> I didn't look at all thread , but did You make: > # mkall /usr/local/midgard ? > > mkall is just a script which calls configure , make , make install and > some testing , doing this that way You point the configure script where > You have header midgard files. mkall no longer uses the value passed to it. Midgard-config must be in your path to succesfully build midgard-php4. We could re-introduce the parameter to have it add it to the PATH during the run of configure. Depending on that is sorta nice, sorta tricky. If there happens to be another midgard- config which is in your path, and the parameter supplied with mkall is off... OK, so that's a pretty contrived example. Personally I think it's a good idea to have config executables in your path, especially if multiple modules make use of it. Plus, 'midgard-config --report' hands out useful info for developers when debugging. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
