Re: automake-1.7.5 Make Error
Hello, current version of Automake is 1.9.6. Why are you trying to build this historic version? FAIL: txinfo5.test ... = 1 of 422 tests failed This test is marked as expected to fail in 1.9.6. So I guess your installation in fact passed the tests. Stepan Kasal
AM_CPPFLAGS not applied for CHECK programs?
I am using automake 1.9.6. Today I was shocked to learn that programs listed in check_PROGRAMS are not built using the same CPPFLAGS options as normal programs. Normal code is built using $(AM_CPPFLAGS) $(CPPFLAGS) but it appears that check programs are only being built using $(CPPFLAGS) so the wrong header files may be used. If it makes any difference, I am using a non-recursive build, and the check programs are in a subdirectory. In my Makefile.am I have been careful to define AM_CPPFLAGS so that it prepares the proper include path to use header files from the build and source directories. Without the extra AM_CPPFLAGS the build is incorrect or fails. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Re: AM_CPPFLAGS not applied for CHECK programs?
Bob == Bob Friesenhahn [EMAIL PROTECTED] writes: Bob As a follow-up to this posting, I see that when Automake generates a Bob specific rule for a target built in a subdirectory, it forgets to Bob include $(AM_CPPFLAGS). This is a serious error. This is documented in the 'Program and Library Variables' node: In compilations with per-target flags, the ordinary `AM_' form of the flags variable is _not_ automatically included in the compilation (however, the user form of the variable _is_ included). So for instance, if you want the hypothetical `maude' compilations to also use the value of `AM_CFLAGS', you would need to write: maude_CFLAGS = ... your flags ... $(AM_CFLAGS) As I recall we made this choice so that people could set a global default and then override it for specific programs. Tom
