[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Incorrect naming of stamp-h* files when using multiple config-headers an

From: Sander Niemeijer
Subject: Incorrect naming of stamp-h* files when using multiple config-headers and automake
Date: Thu, 14 Nov 2002 11:35:25 +0100

I have a package that uses autoconf and automake and contains 2 config header files.


When I first create the config.h and someotherfile.h from their respective .in files the 'configure' script nicely creates a stamp-h1 for config.h and stamp-h2 for someotherfile.h. In automake it also seems that the proper rules are created in which config.h depends on stamp-h1 and someotherfile.h depends on stamp-h2.

The problem now arises when I modify my someotherfile.h.in. Because the .in file has been modified, automake calls '$(SHELL) ./config.status someotherfile.h', but since there is only one config header file in the argument list to config.status, config.status creates a new stamp-h1 file instead of the necessary stamp-h2 file. This means that, since the previous stamp-h2 file was deleted by the automake Makefile, my someotherfile.h keeps on being recreated on every call to make (and of course config.h now depends on a stamph-h1 file with a modification time that is newer than should be)

I think this can be fixed somehow by setting _am_stamp_count in config.status to the occurrence index of the config header filename in the 'config_headers' variable, when creating the stamp-h* file.

I am using the following version of autoconf and automake:
% autoconf --version
autoconf (GNU Autoconf) 2.54

automake --version
automake (GNU automake) 1.7

Since my experience with the inner workings of autoconf are next to nothing, I hope somebody on this list might be able to help to fix this issue. I am afraid that getting myself acquainted with the autoconf sources and creating a patch is a bit beyond what my current workschedule allows.

Thanks in advance for any effort you might put into this!

Sander Niemeijer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]