Mark Carey wrote:
<snip>
> cd /usr/src/sed-4.0.8
> ./configure --prefix=/user --binexecdir=/bin
> : bad interpreter: No such file or directory
> ls /bin/bash
> /bin/bash
> ls -l /bin/sh
> /bin/sh -> bash
<snip>
If you cat the configure script do you see wierd control characters at
the end of each line? I ask because you unpacked all the tarballs on
windows and windows uses a different newline character than unix
systems. That's the only thing I can think of right now.
--
Registered LFS User 6929
Registered Linux User 298182