[Mono-list] RE: Mac X and latest cvs source

[Paolo Molaro]

On 08/20/03 Andy Satori wrote:
> No, this is not the case.
> 
> I have glib-2.0 installed and configured, correctly, that's not the 
> issue.  The error raised by configure isn't that the package isn't 
> installed (pkg-config even knows about glib-2.0 and returns correctly). 
>  I happen to think that we are exposing a bug in either autogen.sh  or 
> configure.  I've attached the corresponding errors for your 
> entertainment :-).
> 
> <!-- log -->
> 
> checking for pkg-config... /usr/local/bin/pkg-config
> ./configure: line 8619: syntax error near unexpected token 
> `PKG_CHECK_MODULES(BASE_DEPENDENCIES,'
> ./configure: line 8619: `PKG_CHECK_MODULES(BASE_DEPENDENCIES, glib-2.0 
> >= $GLIB_REQUIRED_VERSION)'
> 
[...]
> I know next to nothing about shell scripting, so I've now pretty much 
> exhausted my knowledge level on the subject.  PKG_CHECK_MODULES would 
> appear to be a function call, but I don't see it's definition using a 
> grep of the directory doesn't show it being used anywhere else in the 
> build system, so I'm guessing (of the wild ass variety) that this is a 
> dependancy failure, but not one on glib-2.0.

If you use Fink to install the packages, you'll have them all installed
in the same $prefix. People that get that kind of error have some
packages installed in a prefix and some in another (/usr, /usr/local,
/sw, somewhere else).
You need to set the env var ACLOCAL_FLAGS to something like:
ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
before runnin autogen.sh (or run aclocal with the correct arguments
manually). The directory specified in the flags is the one where you
installed glib-2.0.m4.

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better