Re: Autoscan and automake

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

 



According to NightStrike on 2/24/2010 8:37 AM:
> Why doesn't autoscan output the AM_INIT_AUTOMAKE macro into
> configure.scan when it detect Makefile.am, but does output
> AC_CONFIG_FILES([Makefile]), even when Makefile doesn't exist, but
> only Makefile.am does?

Are you sure Makefile.in did not exist?  Showing a shell transcript of a
minimal reproduction of the bug with a bare-bones configure.ac and
Makefile.am might help others reproduce this (as well as be a great
lead-in for a testsuite addition).

The current behavior probably exists because no one has ever reported it
before, or been bothered enough by it to submit a patch.  Unfortunately,
autoscan is not as well tested as autoconf, so any help you could provide
would be welcome.

-- 
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@xxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux