"Derek R. Price" wrote:
> [EMAIL PROTECTED] wrote:
>
> > But in the very same function, if I use $_ instead of @_, which is
> > what the following line does:
>
> $_ isn't set upon function entry in perl. Only @_. The value of your $_ is left
>over from
> somewhere.
>
> By the way, I think I ha
Hello, Ralf!
> $(ACLOCAL_M4): configure.in \
> ./../aclocal/x.m4 \
>
> AFAIS, the "strip "./"" from this patch is to blame for this:
You are right, it's my bug. I'll fix it soon.
Thank you.
Regards,
Pavel Roskin
Hello!
Aclocal didn't follow the GNU standard for the output of non-interactive
programs. Now all messages printed by "aclocal --verbose" will start with
"aclocal: " to make it easier to find them in the autoreconf output.
Regards,
Pavel Roskin
_
--- ChangeLo
[EMAIL PROTECTED] wrote:
> But in the very same function, if I use $_ instead of @_, which is
> what the following line does:
$_ isn't set upon function entry in perl. Only @_. The value of your $_ is left over
from
somewhere.
By the way, I think I have amtraces 99% working. Are we going to
akim <[EMAIL PROTECTED]> writes:
> sub scan_autoconf_config_files
> {
> +print STDERR "=>> @_\n";
> +print STDERR "==>> $_\n";
Why do you expect $_ to contain anything in particular at this point?
You've not assigned anything to it in this sub. $_ is a completely
separate variable fro
Hello, Akim!
> +print STDERR "=>> @_\n";
> +print STDERR "==>> $_\n";
I disagree with this style of programming.
GNU standard says that the program name should start with the name of the
program followed by the colon.
Such patches are sometimes good for debugging, but usually only for
Hi
I think I met a bug in Perl. I'm running
~/src/am % perl --version22:29 remo
This is perl, version 5.005_03 built for i386-linux
Copyright 1987-1999, Larry Wall
Perl may be copied only under the terms of
Tom Tromey <[EMAIL PROTECTED]> writes:
>
> I don't know when I'll fix the bug but it will definitely be before
> the next release.
The bandaid I'm using is below. It seems to work, but it'd be a
mistake to assume I know what I'm doing.
--- automake.in.old Fri Feb 2 06:29:06 2001
+++ automake
When config.status is invoked to regenerate a Makefile, I think it
might be possible to give an empty CONFIG_LINKS and CONFIG_COMMANDS as
well as the current empty CONFIG_HEADERS, to speed up regeneration
when there's a bunch of links.
* automake.in (handle_configure): Call config.status
Tom Tromey wrote:
>
> > "Michael" == Michael Bletzinger <[EMAIL PROTECTED]> writes:
>
> Michael> cvs automake (as of this morning) behaves differently than automake
> Michael> 1.4. 1.4 scanned the SUBDIR targets to locate Makefile.am's.
>
> That's not the case. Automake has always scanned
10 matches
Mail list logo
