Date: Wed, 1 Mar 2000 02:59:56 +0500 (KGT)
From: CyberPsychotic <[EMAIL PROTECTED]>
AC_DEFINE_UNQUOTED([NEED_DECL_]translit($sn_decl, [a-z], [A-Z]), 1,
[you have this cuz autoheader breaks things abit])
This won't work, because translit is an m4 construct, and $sn_decl is
a shell variable. This will convert $sn_decl to $SN_DECL, and let the
shell cope with that.
My macro won't work if you call it with a shell variable, so you can't
call it in a loop.
~ : When used in
~ :BFD, where it is an AC_DEFUN, the $1 is replaced at the m4 level, so
~ :the shell never sees it.
that is what I would expect it too. Maybe m4/autoconf versions differ.
>From what I have seen in configure, these things were not replaced but
rather passed as shell variables.
The $1 presumably was replaced at the m4 level, but that just resolved
it into a shell variable.
~ :In any case, you may want to just pick up the macro that Akim
~ :mentioned that is in the current sources, and use that until the next
~ :autoconf release comes out.
well, the problem here is that we have a few developers working on the
project (cvs), so if I upgrade and use these macros, the other developers
wouldn't be able to generate configure scripts until they upgrade. it
would make a good sence to upgrade in long run anyway, but it would take
some time, so I placed the macro (shown up above) as temporal solution
until everyone in our team would upgrade his autoconf package.
Sorry, I wasn't suggesting that you upgrade to a new version of
autoconf. I was suggesting that you pick up the new macro, and put it
in your acinclude.m4 file, just as you are doing with my macro. If
you rename it, you will avoid any conflicts with future autoconf
releases.
Ian
