[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The demo subdirs
From: |
Tim Van Holder |
Subject: |
Re: The demo subdirs |
Date: |
Fri, 29 Jun 2001 11:13:22 +0200 |
> Current HEAD seems to work okay for me (post Paolo Bonzini's
> autoconf-2.50
Most of this seems automake related.
Start: clean tree
Run bootstrap
-> no libtool or ltmain.sh present
Run configure
-> libtool NOT created (no ltmain.sh, and no Makefile to use to
build ltmain.sh)
Run make
-> make will see libtool missing, and run config.status --recheck
to build it. configure will see no ltmain.sh, so it will run
make to build ltmain.sh. make will run 'config.status --recheck'
again, resulting in an infinite loop.
The same happens if configure is re-run, or even if
'make ltmain.sh' is run. The apparent cause is the automake I use
(a CVS snapshot); it adds a rule
$(top_builddir)/config.status: $(srcdir)/configure
$(CONFIG_STATUS_DEPENDENCIES)
$(SHELL) ./config.status --recheck
to the makefile, and since Makefile depends on config.status, this
gets triggered all the time.
Removing it allows building ltmain.sh - the saga continues:
Run make
-> ltmain.sh is built, and config.status --recheck is run, libtool is
created. make descends into libltdl - there the build stops because
libtool is not found ($(OBJECTS) depends on libtool, but there is
no OBJECTS variable, just libltdl(c)_la_OBJECTS)
Run make distclean
-> fails immediately (it enters tagdemo, which has no Makefile, and
therefore no distclean target).
Basically, we want config.status to be the one to create both ltmain.sh
and libtool; otherwise, make can really screw things up (especially in
combination with recent automakes).
And I think we want configure to configure the demo subdirs as well.
I'll take a stab at the 2.50-fication of the creation of libtool/ltmain.sh
next week.