Re: "include $(top_builddir)/aminclude.am" is ignored by automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Alexandre Duret-Lutz wrote: > If you want to portably include (non-automake) Makefile fragment, > don't use include. Instead try to use AC_SUBST_FILE, or (IMHO better) > something like AC_CONFIG_FILES([Makefile:Makefile.in:fragment.mk]). Perfect

Re: "include $(top_builddir)/aminclude.am" is ignored by automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Alexandre, I wrote: > Alexandre Duret-Lutz wrote: > >>>If you want to portably include (non-automake) Makefile fragment, >>>don't use include. Instead try to use AC_SUBST_FILE, or (IMHO better) >>>something like AC_CONFIG_FILES([Makefile:Makefile

Use of really long lines in Makefile.in

Should automake split long lines? During the sed substitution in autoconf, the default sed used on Solaris 2.6 and 7 will truncate long lines in Makefile.in's. I submitted a patch to autoconf to use the "best" sed available on the system but Paul Eggert brought up the issue of the invalid use of lo

Re: Use of really long lines in Makefile.in

Albert Chin <[EMAIL PROTECTED]> writes: > So, should automake change lines like: > foo_SOURCES = [long list of sources] > to the following in Makefile.in: > foo_SOURCES = $(foo_SOURCES_1) $(foo_SOURCES_2) ... > foo_SOURCES_1 = [list of sources < 2048 chars] > foo_SOURCES_2 = [list of source

Running ./config.status

Hi, I proposed to the following change to a autoconf/tests/Makefile.am[1]: atconfig: $(top_builddir)/config.status - cd $(top_builddir) && ./config.status $(subdir)/$@ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ On Thu, Feb 03, 2005 at 12:59:28PM -0800, Paul Egg