Re: bjam in gcc 2.95

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-25 19:52:13

"John Maddock" <john_at_[hidden]> writes:

>> When trying to run build.sh by just typing
>> "./build.sh" it gives a "bad interpreter error". When
>> using "sh ./build.sh" (like in the boost docs), it
>> returns several "unknown command" errors followed by a
>> syntax error near the first defined function in the
>> script (specifying the toolset like "sh ./build.sh
>> gcc" shows the same behaviour).
>
> You can get that with shell scripts if they have *windows line endings*. If 
> you got the source from the windows zip file, then you will almost certainly 
> need to strip the \r's from the shell script before it'll be accepted by the 
> shell (you can do that with the tr command, but I forget the exact 
> invocation).

If that's the case, you're better off downloading the .tgz or getting
it directly from CVS. You never know what other problems lurk after
you fix the windows line endings in that one file.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com