From: Keith M. <kei...@us...> - 2008-05-09 20:17:35
|
On Wednesday 30 April 2008 15:49, Cesar Strauss wrote: > Tripp wrote: > > $ make install > > Makefile:678: warning: overriding commands for target `install' > > Makefile:574: warning: ignoring old commands for target `install' > > The makefile seems to be using case sensitive patterns (i.e. install > and INSTALL). FWIW, I got back to the office this week, and gave autoconf-2.62 a try, building from pristine FSF source, using MSYS-1.0.11. I did *not* do this... > Please try using "csmake install" instead of "make install". ...yet I had no problem in either building or installing, and after fixing a minor issue in the testsuite, (and seven hours of run time), I was also able to run that with complete success. So, why did I fail to reproduce Tripp's failure? Here's what I did:-- 1) Download and extract ftp.gnu.org/gnu/autoconf/autoconf-2.62.tar.bz2 2) mkdir -p build/autoconf-2.62 3) cd build/autoconf-2.62 4) ../../autoconf-2.62/configure 5) make 6) make install This all completed without any problem whatsoever, so I guessed that maybe Tripp did his build in the source directory, (something I never do, if it is avoidable), and sure enough, if I do that, then I *can* reproduce his problem. So, it seems that this Makefile rule... > $(srcdir)/INSTALL: $(top_srcdir)/doc/install.texi > $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -o $@ \ > $(top_srcdir)/doc/install.texi ...found at Makefile line 677, (with commands starting at line 678), conflicts with this one... | install: $(BUILT_SOURCES) | $(MAKE) $(AM_MAKEFLAGS) install-recursive ...(found at lines 573/574), if, and only if, make is (correctly, IMO) configured to respect the fundamentally case-insensitive nature of the Win32 file system, *and* $(srcdir) is identically equal to `.', (as will be the case when building within the source directory). This issue may be resolved by replacing each of the three references to `$(srcdir)/INSTALL', in the Makefile, by `$(abs_srcdir)/INSTALL'. IMO, this is a more technically appropriate solution to the problem, than the symptomatic workaround of using csmake in preference to make, so I am `putting my money where my mouth is', and I have filed a bug report, and proposed patch, with bug...@gn... accordingly. Regards, Keith. |