Am Mit, 2002-09-18 um 23.23 schrieb Alexandre Duret-Lutz:
> Please SHOUT LOUD if your package works with Automake 1.6.3 but
> doesn't with 1.6d.
This bug has been present with previous versions of automake and
autoconf (IIRC, it also has been reported several times before).
Anyway, it is still
>>> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
[...]
Pavel> Well, my package doesn't. Here's the test (full test
Pavel> with copyright is attached):
Thanks a lot! I'm installing the following fix.
2002-09-19 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.in (requir
>>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
[...]
Ralf> automake-1.6d complains about this:
Ralf> # cat Makefile.am
Ralf> .PHONY: foo
Ralf> .PHONY: bar
Ralf> # automake
Ralf> Makefile.am:2: redefinition of `.PHONY'...
Ralf> Makefile.am:1: ... `.PHONY' previously defined her
>>> "Schleicher" == Schleicher Ralph (LLI) <[EMAIL PROTECTED]> writes:
[...]
Schleicher> I think there is an inconsistency between the
Schleicher> Automake documentation and actual program behavior.
Thanks a lot! I'm checking this in.
2002-09-19 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
>>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> This bug has been present with previous versions of automake and
Ralf> autoconf (IIRC, it also has been reported several times before).
I think this is the same issue as
http://mail.gnu.org/pipermail/libtool/2002-August/006640.h
Hi There
The following problem drives me crazy:
I have a little C++ signal-slot library, that consists of only two C++ header
files. The automake script should do the following:
Sources are:
sig/functor.hxx.m4
sig/sigslot.hxx.m4
sig/macros.m4
Targets are:
sig/functor.hxx
sig/sigslot
Hello!
The attached script may seem gross, but it does its job - using just sed
and perl, it creates temporary aclocal and automake, which recreate
aclocal.m4 and Makefile.in in all directories, and the later are exactly
the same as those currently on CVS.
Bootstrapping Automake from CVS is quit
> The attached script may seem gross, but it does its job - using just sed
> and perl, it creates temporary aclocal and automake, which recreate
> aclocal.m4 and Makefile.in in all directories, and the later are exactly
> the same as those currently on CVS.
I'm sorry, that was a preliminary versi
Pavel Roskin wrote:
> I won't object if this script is renamed to autogen.sh
I will, tho. :-)
Bruce Korb wrote:
>
> Pavel Roskin wrote:
>
> > I won't object if this script is renamed to autogen.sh
>
> I will, tho. :-)
I will too, unless you've used autogen to create it.
Earnie.
Hello, Alexandre!
> Pavel> Well, my package doesn't. Here's the test (full test
> Pavel> with copyright is attached):
>
> Thanks a lot! I'm installing the following fix.
The fix works. GNU Midnight Commander works with CVS Automake now. Thank
you!
--
Regards,
Pavel Roskin
Hello!
warnopts.test fails randomly for me. I have just applied this patch
that fixes the problem:
* tests/warnopts.test: Fix random failures by removing Autoconf
cache directory when configure.in changes. Use the code and the
comment from tests/asm.test.
I was wondering if someone knew what these error message meant:
Makefile:483: warning: overriding commands for target
`engine/cpp/engine.o'
Makefile:362: warning: ignoring old commands for target
`engine/cpp/engine.o'
Makefile:489: warning: overriding commands for target
`engine/cpp/engine.obj'
M
Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> >>> "Roger" == Roger Leigh <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Roger> However, this makes one very big assumption: every
> Roger> installation directory will use $prefix as the path
> Roger> prefix.
>
> Yes. This way we make sure peo
http://www.chattamela.com
servizi x adulti
http://www.chattamela.com
foto, film,webcam, molto esplicitiv.m.
se vuoi cancellarti dalla mailing list scrvi a:
[EMAIL PROTECTED]
Is there anything in the CVS repo that will not be part of the next automake
release?
IE, what do I want to use if I want to get the release candidate?
H
Hello!
It has occured to me that the complex "distcheck" procedure doesn't have
to be integrated into Automake. In fact, "make distcheck" works with the
tarball and treats it as a black box.
Automake knows a lot about most of the files and can generate rules that
work with those files. But the
Pavel Roskin wrote:
>
> Hello!
> At some point, "make distcheck" would simply call "make dist" and run the
> standalone "distcheck" script with predefined DISTCHECK_FLAGS.
YES!
Am Don, 2002-09-19 um 10.59 schrieb Alexandre Duret-Lutz:
> >>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Ralf> automake-1.6d complains about this:
>
> Ralf> # cat Makefile.am
> Ralf> .PHONY: foo
> Ralf> .PHONY: bar
>
> Ralf> # automake
> Ralf> Makefile.am:2: red
Am Don, 2002-09-19 um 11.36 schrieb Alexandre Duret-Lutz:
> >>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>
> Ralf> This bug has been present with previous versions of automake and
> Ralf> autoconf (IIRC, it also has been reported several times before).
>
> I think this is the same
20 matches
Mail list logo
