Build scripts on 64-bit Linux

[alex]

I have a constant problem with build scripts on a 64-bit AMD Linux box (Gentoo).
The error message is 'bad interpreter'.
Apparently, it has to do with file format, because all I have to do is simply open the offending files (makedepend.gcc, projname and shlibln) and save them (without any modification).

This does not happen on 32-bit Linux.

Once you know it, it is a minor annoyance, but when encountered for the first time, it can consume a good chunk of time.

Does anyone have an idea why is this happening and how to fix it?

Alex

[alex]

Correction/update:

Same thing just happened to me on a 32-bit Gentoo box.
Looks like a line-ending issue in the distribution archive scripts.

Here's a sample:

sh: /shared/poco/build/script/shlibln: /bin/sh^M: bad interpreter: No such file or directory
make[1]: *** [/shared/poco/lib/Linux/i686/libPocoFoundationd.so.2] Error 126
make[1]: Leaving directory `/shared/poco/Foundation'

Alex

[peter]

Hi Alex,
definitely line ending problem. We actually thought we squished them with 1.2.5.
We'll look into it, fixed with the next version.

thx,
Peter

> I have a constant problem with build scripts on a 64-bit AMD Linux box (Gentoo).
> The error message is 'bad interpreter'.
> Apparently, it has to do with file format, because all I have to do is simply open the offending files (makedepend.gcc, projname and shlibln) and save them (without any modification).
>
> This does not happen on 32-bit Linux.
>
> Once you know it, it is a minor annoyance, but when encountered for the first time, it can consume a good chunk of time.
>
> Does anyone have an idea why is this happening and how to fix it?
>
> Alex

[peter]

Damn it,
I actually hoped we squished them with 1.2.5.

Will be fixed in the next release.
thx
Peter

> I have a constant problem with build scripts on a 64-bit AMD Linux box (Gentoo).
> The error message is 'bad interpreter'.
> Apparently, it has to do with file format, because all I have to do is simply open the offending files (makedepend.gcc, projname and shlibln) and save them (without any modification).
>
> This does not happen on 32-bit Linux.
>
> Once you know it, it is a minor annoyance, but when encountered for the first time, it can consume a good chunk of time.
>
> Does anyone have an idea why is this happening and how to fix it?
>
> Alex