> -----Original Message-----
> From: OpenMacNews [mailto:openmacnews@gmail.com]
> Sent: 27 February 2006 16:27
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Buildproblems on OSX 10.3 due
> to libxml2
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> > Why's it even being called? We don't create any libraries
> at all (and I
> > never saw any warnings about it on Tiger, or back when I was running
> > Panther).
>
> well, glibtoolize is being called cuz i'm calling it ... as i
> typically
> do given that i've a rather up-to-date env. just cleaning
> house, as it
> were.
>
> as for why glibtoolize is 'calling' AC_PROG_LIBTOOL, that's
> to be found
> in libtool.m4:
OK, you'll have to excuse my bumbling ignorance when it comes to all
things automake/autoconf - why are you running glibtoolize in the
pgAdmin source directory? The bootstrap script does everything that's
required from a clean SVN checkout, and is also sufficient to rebuild
things if you change anything.
Regards, Dave
