On Sat, 13 Nov 2010, Raymond Toy wrote:
< On 11/12/10 11:19 AM, Robert Dodier wrote:
< > Ray, I tried it again on a different system (also Linux)
< > and ./configure works OK. One difference (dunno what
< > others there might be) is that autoconf is 2.61 on the
< > system where ./configure works and 2.59 on the one
< > where it doesn't work.
< >
< Perhaps that's the problem. The oldest version I have is 2.61. The
< oldest version of automake I have is 1.10.
< > I do get some warnings from sh bootstrap on the system
< > for which ./configure works. I've appended them below.
< >
< > best
< >
< > Robert Dodier
< >
< > PS.
< > $ sh bootstrap
< > + aclocal
< > + automake --add-missing --copy
< > src/Makefile.am:314: `%'-style pattern rules are a GNU make extension
< > src/Makefile.am:315: subst echo_,,$@: non-POSIX variable name
< > src/Makefile.am:315: (probably a GNU make extension)
< > src/Makefile.am:315: $(subst echo_,,$@: non-POSIX variable name
< > src/Makefile.am:315: (probably a GNU make extension)
< > src/Makefile.am:316: subst echo_,,$@: non-POSIX variable name
< > src/Makefile.am:316: (probably a GNU make extension)
< > src/Makefile.am:316: origin $(subst echo_,,$@: non-POSIX variable name
< > src/Makefile.am:316: (probably a GNU make extension)
< > + autoconf
< >
< I've seen these messages since forever, so this isn't caused by the
< recent changes.
Is there a reason those lines are written like they are?
I would write them as
echo_%:
@echo "$*=$($*)"
@echo "origin $* returns $(origin $*)"
We are still using non-POSIX constructs, but the code & complaint are more
intelligible:
src/Makefile.am:314: `%'-style pattern rules are a GNU make extension
src/Makefile.am:315: $*: non-POSIX variable name
src/Makefile.am:316: origin $*: non-POSIX variable name
src/Makefile.am:316: (probably a GNU make extension)
Leo
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.