[Bug-gnupod] Configure as_echo fix

2009-07-03 Thread Richard van den Berg
Configure has always printed -n strings on my MacBook. I fixed that by using as_echo and as_echo_n. See my patch on the rvdb/configure-fix branch. Cheers, Richard ___ Bug-gnupod mailing list Bug-gnupod@nongnu.org

Re: [Bug-gnupod] Configure as_echo fix

2009-07-03 Thread H. Langos
On Fri, Jul 03, 2009 at 08:37:20PM +0200, Richard van den Berg wrote: Configure has always printed -n strings on my MacBook. I fixed that by using as_echo and as_echo_n. See my patch on the rvdb/configure-fix branch. Looks good so far. I'll merge it. It's probably a shell oddity of the echo

Re: [Bug-gnupod] Configure as_echo fix

2009-07-03 Thread Richard van den Berg
On 7/3/09 9:59 PM, H. Langos wrote: Which mac os version did you use? OS X 10.5.7 The default Mac OS X sh was originally Zsh; it was changed to Bash in Mac OS X 10.2. I definitely use bash. If it wasn't the default, I would have changed it. :-) Do you happen to know if

Re: [Bug-gnupod] Configure as_echo fix

2009-07-03 Thread H. Langos
On Fri, Jul 03, 2009 at 10:06:58PM +0200, Richard van den Berg wrote: On 7/3/09 9:59 PM, H. Langos wrote: Which mac os version did you use? OS X 10.5.7 The default Mac OS X sh was originally Zsh; it was changed to Bash in Mac OS X 10.2. I definitely use bash. If it

Re: [Bug-gnupod] Configure as_echo fix

2009-07-03 Thread Richard van den Berg
On 7/3/09 10:55 PM, H. Langos wrote: But it seems that autoconf itself is not covered by the posix standard. I assumed you already knew that. :-) Where did you find the hint to replace echo $ECHO_N by $as_echo_n? From the generated configure script. I wouldn't be surprised if the