~ :
~ :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.
oops.. yep. Noticed that :-\ Thanks.
~ :My macro won't work if you call it with a shell variable, so you can't
~ :call it in a loop.
yeah, also figured it out just now :)
~ : 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.
yes. That is what I have seen there.
~ :
~ :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.
Opps.. I didn't know about it. I usually place macros into configure.in or
some randomly named file and then do `include(./filename.m4)' from
configure.in. Would it make difference if I name file `acinclude.m4'?
~ : If
~ :you rename it, you will avoid any conflicts with future autoconf
~ :releases.
~ :
Yeah, I will probably go for it, thanks.
