Following up on a discussion in the Autoconf and Automake mailing
lists, here's a proposed patch to Automake to have it test better for
file names with funny characters. If you look for the
expected_build_failures and expected_install_failures variables,
you'll see the test cases that
Hello,
thanks for your interesting contribution.
On Sat, Jun 11, 2005 at 12:36:17AM +1000, John Vandenberg wrote:
I recently accidently ran into a ~10% performance improvement in
aclocal. The attached patch requests autom4te only traces 'defun'
macros that aclocal has noticed, rather than a
Hi,
a bug report pointed me to AC_PROG_CC_C_O.
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
ad 1) Special needs of a project should be solved in that project.
ad 2) The comments in automake/m4/minuso.m4 explain why Automake is not
happy with the
Hi Stepan,
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
If yes, shouldn't we introduce a generalized macro, for example
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
Hi Stepan,
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
All
* Ralf Corsepius wrote on Fri, Jul 01, 2005 at 03:20:22PM CEST:
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do
On Fri, 2005-07-01 at 15:23 +0200, Ralf Wildenhues wrote:
* Ralf Corsepius wrote on Fri, Jul 01, 2005 at 03:20:22PM CEST:
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU
Hello,
On Fri, Jul 01, 2005 at 02:33:57PM +0200, Ralf Wildenhues wrote:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
Of course I don't know. But it's so poorly designed, that I think it's
Hi,
On Fri, Jul 01, 2005 at 04:08:50PM +0200, Ralf Corsepius wrote:
All packages using subdir-objects (Flat Makefiles in deep source trees
support) currently are using it.
...
Yep, I am referring to AM_PROG_CC_C_O, which according to the comment
above internally uses AC_PROG_CC_C_O.
Of
Hi all;
I got no real response to this. This release of GNU make (3.81) is
coming up (one hopes!) and this seems like a real problem that we need
to come up with a solution for. If we don't it seems like automake and
GNU make 3.81 and Java simply will not be usable together.
Anyone have any
I figured out the problem: for some reason, I couldn't just specify the
option in the top-level Makefile.am. I had to specify it in the src
directory's Makefile.am. (How come?)
Thus spake Ralf Wildenhues on 6/30/2005 6:29 PM:
* overbored wrote on Fri, Jul 01, 2005 at 12:44:38AM CEST:
Thus
FYI, here's one way to handle it (obviously requires GNU make):
ifeq (,$(filter second-expansion,$(.FEATURES)))
# GNU make 3.81
PRE_D := $$
else
# GNU make =3.81
PRE_D :=
endif
# Now use PRE_D in prerequisites
all: foo$(PRE_D)bar ; @echo '$@: $'
foo$$bar: ;
pds == Paul D Smith [EMAIL PROTECTED] writes:
pds Hi all;
pds I got no real response to this. This release of GNU make (3.81) is
pds coming up (one hopes!) and this seems like a real problem that we need
pds to come up with a solution for. If we don't it seems like automake and
pds GNU
pds == Paul D Smith [EMAIL PROTECTED] writes:
pds FYI, here's one way to handle it (obviously requires GNU make):
pds ifeq (,$(filter second-expansion,$(.FEATURES)))
pds # GNU make 3.81
pds PRE_D := $$
pds else
pds # GNU make =3.81
pds PRE_D :=
pds endif
pds # Now use PRE_D in
14 matches
Mail list logo
