bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Internal error (weird)


From: John-John Tedro
Subject: Re: Internal error (weird)
Date: Wed, 10 Oct 2007 21:38:00 +0200



On 10/8/07, Ralf Wildenhues <address@hidden> wrote:
Hello John-John,

Thanks for the report.

* John-John Tedro wrote on Mon, Oct 08, 2007 at 12:16:46PM CEST:
>
> Use of uninitialized value in exists at /usr/bin/automake-1.10 line 4823,
> <GEN0> line 1.
> Use of uninitialized value in concatenation (.) or string at
> /usr/bin/automake-1.10 line 4823, <GEN0> line 1.
> automake-1.10: ####################
> automake-1.10: ## Internal Error ##
> automake-1.10: ####################
> automake-1.10: unrequested trace `'
> automake-1.10: Please contact <address@hidden>.
>  at /usr/share/automake- 1.10/Automake/Channels.pm line 570
>         Automake::Channels::msg('automake', '', 'unrequested trace `\'')
> called at /usr/share/automake-1.10/Automake/ChannelDefs.pm line 191
>         Automake::ChannelDefs::prog_error('unrequested trace `\'') called at
> /usr/bin/automake-1.10 line 4823
>         Automake::scan_autoconf_traces('configure.ac ') called at
> /usr/bin/automake-1.10 line 5046
>         Automake::scan_autoconf_files() called at
> /usr/bin/automake-1.10line 7811
>
> Im running this on a Gentoo x86. It occurs even if configure.ac is empty.

Can you run
  /usr/bin/automake-1.10 --verbose

and post the output?  Thanks.

> Also autoconf _always_ gives:

You mean, running `./configure' outputs the following, no?

> as_func_failure succeeded.
> as_func_failure succeeded.
>
> Not typo, it says it twice, no matter what you do.
> And it's _not_ shell dependant, tested it with bash and zsh.

How exactly do you invoke configure?  Do you have $SHELL or
$CONFIG_SHELL set in the environment?  Where are bash and zsh installed,
and which exact versions are they?  If you've compiled them yourself, or
if you or Gentoo have applied any patches to these shells, could you
provide pointers to them?

Cheers,
Ralf

I had /bin/sh linked to zsh, this was the problem, must be some bug in the zsh parser (if it's 100% sh compatible).
I think i should take this with the zsh devs instead : P.

I linked /bin/sh to bash, so now it's working.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]