Re: automake/472: toolchain issues when building *.o files from *.S files
Hello Seth, On Mon, Aug 15, 2005 at 06:48:45PM -0700, Seth Brutzman wrote: The patch worked beautifully! I applied it to my tarball-compile of automake 1.9.6, then recompiled Inkscape without so much as a hiccup. Thanks for the prompt reply and spot on fix. :) I was lucky. ;-) I've passed along the patch to the Inkscape developers with the news that it works like a charm. Fantastic job! Unfortunately, the need for patched Automake might complicate things. The developpers can use it to generate tarballs, but people who would like to compile from CVS would be trapped. It might be worth it to think a bit more about possible workarounds: 1) you could look at your generated Makefile.in and copy the rule .S.o: to inkscape/src/Makefile.am. That explicit rule would override the Automake supplied one, even for unpatched versions of Automake. 2) if libnr/libnr were a libtool library, declared by noinst_LTLIBRARIES = libnr/libnr.la things should work without any patch. I think that any of these workarounds would be more convenient for the maintainers than requiring patched Automake. Of course, this presents more work for you, Seth: you have to reinstall vanilla Automake and verify that the workarounds really works in your environment. Happy hacking! ;-) Stepan Kasal
how to extend the Makefile templates?
Hi folks, I would need some way to add recursive targets to all generated Makefiles, without asking every owner of every Makefile.am to append some include statement or some keyword to be replaced by AC_SUBST_FILE. What would be your suggestion to solve this? Regards Harri
Re: how to extend the Makefile templates?
Hi Harald, * Harald Dunkel wrote on Tue, Aug 16, 2005 at 12:39:46PM CEST: I would need some way to add recursive targets to all generated Makefiles, without asking every owner of every Makefile.am to append some include statement or some keyword to be replaced by AC_SUBST_FILE. Hmm. I remember you asking a similar question before. What would be your suggestion to solve this? I don't have a good answer to your specific question at the moment (short of extending Automake). But I have a suggestion for questions such as yours: For other people (e.g. me), requirements such as above would be much easier to understand if a good reason for it was given as well. I mean, what is it that prevents you from doing something like this find $top_srcdir -name Makefile.am | while read file do echo 'include $top_srcdir/some_snippet.am' $file done once and for all? Cheers, Ralf
Files used in EXTRA_DIST not working with distcheck
I have two files, cspm.lex and cspm.y that due to circumstances out of my control need special processing. The only way I could get them into the package without automake automatically processing them was by using the EXTRA_DIST variable, as follows EXTRA_DIST = cspm.lex cspm.y I can make dist, and the package works fine. However, make distcheck always fails with the following error bison -v -d cspm.y bison: cannot open file `cspm.y': No such file or directory It appears as if distcheck is not including the EXTRA_DIST files in its check. Is there any way I can force distcheck to include EXTRA_DIST files during checking? Thanks, Joshua Moore-Oliva
