Hello, Akim and Tom!
> Pavel> The problem happens quite often because install cannot
> Pavel> overwrite running executable files and happily goes ahead and
> Pavel> installs data files. I have been fooled by this two or three
> Pavel> times.
>
> I can't reproduce it with ash. Could you write s
Hi. I have a project (collection of configure.in, Makefile.am's,
etc.) that automake 1.4 worked fine on. But when I try automake 1.5 I
get all sorts of errors. To me, it looks like the behavior of
`include' might have changed, but I don't see anything automake's NEWS
or Changelog files to sugge
On Thu, 2002-08-29 at 10:57, Akim Demaille wrote:
>
> | There are compilers which don't accept `.cc' but need `.cpp' for C++
> | files. Among them are z/OS (by default) and various compilers for
> | MS-DOS and Windows. What about support for a CXXEXT variable? It is
> | quite easy to add a rul
| There are compilers which don't accept `.cc' but need `.cpp' for C++
| files. Among them are z/OS (by default) and various compilers for
| MS-DOS and Windows. What about support for a CXXEXT variable? It is
| quite easy to add a rule
|
| .cc.cpp:
| $(CP) $< $@
Well, this is a problem
(Why bug-autoconf???)
| Is the use of variables in implicit rules portable?
|
| .c.$(OBJEXT):
| ...
I don't know. Maybe Automake folks do?
