Re: [Etherboot-developers] [Etherboot-discuss] __divdi3.c.d:13: *** missing separator. Stop.

[Jim M. <jam@McQuil.com>]

To overcome issues with built-in echo not accepting the '-e' option, 
i've gotten into the habit of forcing it to use the non-built-in echo.

So far, I've never been bit by doing:

     /bin/echo -e "blah blah\n"


Maybe it'll work for you too.

Jim McQuillan
jam@Ltsp.org




Michael Brown wrote:
> On Sat, 8 Sep 2007, Michael Hughes wrote:
>>> Yes, that's the "echo -e" problem.  Your shell doesn't require a "-e" 
>>> option (which is fine), but does ignore the "-e" option and treat it 
>>> as part of the text to echo out (which is not).
>>>
>>> We have code to detect this in src/Makefile.housekeeping:
>>>
>>>   # Check for correct syntax for echo -e
>>>   #
>>>   ifeq ($(shell echo '\0101'),A)
>>>   ECHO_E = echo
>>>   else
>>>   ECHO_E = echo -e
>>>   endif
>>>
>>> so I'd be interested to learn what your shell produces when you type
>>>
>>>   echo '\0101'
>> OK - Here's my output:
>>
>> michael@smallfry:~$ echo '\0101'
>> \0101
>> michael@smallfry:~$
> 
> Interesting.  Which pathological shell is this?  Can you send me 
> (off-list, if it's large) a copy of the man page?
> 
>> doesn't the project use something like:
>> #!/bin/bash
>> to dictate which shell to use?
> 
> No; this is the shell which make chooses to spawn.  We could set the SHELL 
> variable to /bin/bash, but I'd prefer to avoid requiring a shell that may 
> not be installed.
> 
> Michael
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers