« Return to Thread: AS_ECHO calls finding their way into calls

Re: AS_ECHO calls finding their way into calls

by BJ Terry :: Rate this Message:

Eric,

It appears that you are right, and thanks for your help. When I
upgraded to 2.63 on my machine it now exhibits the same problem.
Digging around through all of the m4 files it looks like the offending
function is

In 2.63 (erlang.m4):

# AC_LANG(Erlang)
# ---------------
m4_define([AC_LANG(Erlang)],
[ac_ext=erl
ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD'
ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD ; echo "#!/bin/sh" > conftest$ac_exeext ;
AS_ECHO(["\"$ERL\" -run conftest start -run init stop -noshell"]) >>
conftest$ac_exeext ; chmod +x conftest$ac_exeext'
])

In 2.60 (erlang.m4):

# AC_LANG(Erlang)
# ---------------
m4_define([AC_LANG(Erlang)],
[ac_ext=erl
ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD'
ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD ; echo "#!/bin/sh" > conftest$ac_exeext ; echo
"\"$ERL\" -run conftest start -run init stop -noshell" >> conftest
$ac_exeext ; chmod +x conftest$ac_exeext'
])

I guess to fix this you would change it to read

# AC_LANG(Erlang)
# ---------------
m4_define([AC_LANG(Erlang)],
[ac_ext=erl
ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD'
ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext
>&AS_MESSAGE_LOG_FD ; echo "#!/bin/sh" > conftest$ac_exeext ;
$as_echo $ERL -run conftest start -run init stop -noshell >> conftest
$ac_exeext ; chmod +x conftest$ac_exeext'
])

But why is there another echo statement in there? Do they each do
something different?

On Sep 15, 2008, at 4:17 AM, Eric Blake wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to BJ Terry on 9/15/2008 12:28 AM:
>>
>> AC_INIT
>>
>> AC_ERLANG_CHECK_LIB(erl_interface)
>
> I'm not as familiar with Erlang, so it very well could be that you've
> discovered a bug in autoconf.
>
>>
>> Now, I did note that his has $as_echo wherever mine had just echo,
>> and I
>> don't know why that is, and don't know why google couldn't provide
>> any
>> useful links on the matter.
>
> Because the use of 'echo' is not always portable, so newer autoconf
> guarantees a safe fallback (such as printf) in case it has detected
> that
> your shell's echo does not fit autoconf's needs.
>
>> The real problem appears to be that his
>> "ac_link" variable has AS_ECHO in it instead of echo, which seems
>> like
>> it would cause problems to me.
>>
>> For the record, I am using autoconf 2.60 and M4 version 1.4.5, and
>> he is
>> using autoconf 2.62 and M4 version 1.4.11. My platform is Mac OS X
>> 10.5
>> running fink versions of these tools and he is using Mac OS X 10.4
>> running the darwinports version, if that makes any difference.
>
> It looks like you are reporting a regression that occurred sometime
> between 2.60 and 2.62. Could you please check whether 2.63 also has
> the
> bug, so we can fix it?
>
> - --
> Don't work too hard, make some time for fun as well!
>
> Eric Blake ebb9@...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkjORF4ACgkQ84KuGfSFAYCsfgCgsyKxi1ACHnSfN0iLYJhTZm7S
> gvUAnj96rSbrFWWeFe923PqukR2sFiie
> =oxP8
> -----END PGP SIGNATURE-----

_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

« Return to Thread: AS_ECHO calls finding their way into calls