Re: [Mesa3d-dev] GGI

[Sven M. H. <pe...@gm...>]

On Thu, Dec 21, 2000 at 02:28:57PM -0800, Jon Taylor wrote:
> GGI extensions (of which GGIMesa is one) require the auto* build system 
> to be used.

OK, I understand.

> > Looks ugly. My last try on compiling with autoconfmake chocked on the GGI
> > driver, too. Disabling it in configure.in, OK?
> 
> 	It works fine for me.  Do you have GGI installed, or no?  Anyway, the 

Yes I have. But maybe it's an old version. I'll reenable the GGI code in
configure.in, my fault.


> whole build is now broken for me:
> 
> $ ./bootstrap
> 
> autoheader: error: AC_CONFIG_HEADERS not found in configure.in
Makes no sense: AM_CONFIG_HEADER is used.
> automake: no `Makefile.am' found or specified
Makes no sense: Makefile.am is there.
> configure.in:3: error: Autoconf version 2.49c or higher is required for 
> this script

I guess the first two errors are caused by autoconf/automake choking because
of my use of autoconf 2.49c.

> 	The latest version of autoconf on alpha.gnu.org is 2.49b.  Where can I 
> find 2.49c and why is it necessary to use the absolute newest test 
> releases of autoconf?

2.49c is in CVS (:pserver:an...@su...:/cvs). I use it because
I just like getting all the latest features and I figured it would be suitable
to have it used in development. First thing that comes to mind right now is
the AC_CONFIG_FILES macro that conveniently allows dynamic specification of
output files.

There's only one inconvenience: The newest automake doesn't deal with the
newest libtool correctly: It requires the ltconfig script which is no longer
used by libtool. It is simple, however to patch the current CVS version of
automake: in line 196 remove ltconfig from @libtoolize_files. That's it.



-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]