> 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.
As noted in the INSTALL file, midgard-lib installs midgard-config in
${prefix}/bin, which you need to make sure is in your path.
> 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)
We could indeed have added ${prefix}/bin to PATH for the duration of the
configure run. Worth considering. The workaround, in the meantime, is to
make sure midgard-config is in your PATH.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
