Michael Jennings wrote:
usually output by autoconf 2.5x. For example, eliminating the use
of acconfig.h, adding the description parameter to AC_DEFINEs
etc. It is


If acconfig.h is eliminated, what file will be used to generate
config.h.in?

Do not remove the acconfig.h or any other files needed by autoconf
2.13.  If 2.5x give you warnings, and you can fix them without
screwing up 2.13, that's fine.  But the severe beating of the guilty
party will be required should someone break the build.

Quoting config.h.in for e16 generated on RH-7.2 (auto{conf,header}-2.13):

"/* config.h.in. Generated automatically from configure.in by autoheader. */"

/Kim


------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to