On Thu, Feb 20, 2003 at 04:55:17PM -0000, James Spedding wrote:
> > But since it does find /usr/local/bin/midgard-config, but appearantly
> > not midgard.h, it looks like you have a mix of an old and a newer
> > midgard-lib on the system. I would expect configure to look for
> > midgard/midgard.h, not just midgard.h
>
> I'm not sure what to do next though - can I clean up after the old one or will it
>get round the problem by using the --with-midgard-config?
If you don't need the old one, clean it up. You can run
$ /usr/local/bin/midgard-config --report
to see what went where during its install. Clean out midgard libraries and the
midgard include directories from there, then remove this midgard-config.
You want to be using the one from /usr/local/midgard/bin.
It is possible to have two side-by-side midgard-lib installations. I'd
just prefer not to.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
