[Nasm-devel] Bad line endings in configure file in zip file
H. Peter Anvin
hpa at zytor.com
Mon Feb 5 13:27:30 PST 2024
It isn't an error; the .zip file has DOS-style file endings because it
is intended primarily to be used on DOS/Windows and similar systems.
On Unix, you can extract it with "unzip -a" or (better) use the .tar.xz
file.
-hpa
On 2/5/24 13:15, Keith Thompson wrote:
> In https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/nasm-2.16.01.zip
> <https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/nasm-2.16.01.zip>,
> the configure script has Windows-style CRLF line endings. This makes it
> impossible to run, either with ./configure or sh ./configure:
>
> $ ./configure
> bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory
> $ sh ./configure
> : not found: 15:
> ./configure: 33: Syntax error: newline unexpected (expecting ")")
> $
>
> I used "unzip -b" on Ubuntu, which turns off any text format conversions
> and treats all files as binary, so the problem isn't in how the files
> are unpacked.
>
> I haven't checked other files.
>
> My guess is that this hasn't been noticed because most users would
> download a tarball rather than a zipfile. The .tar.gz file is correct.
>
> _______________________________________________
> Nasm-devel mailing list
> Nasm-devel at nasm.us
> https://lists.nasm.us/nasm-devel
More information about the Nasm-devel
mailing list