-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build: freecol
script is not executable and uses wrong line-endings
#108
Comments
The only place in build.xml that refers to the freecol script is where it simply copies it into the build staging directory. Looks like an installer/packager problem, not something in our code. |
I took a look at the ant documentation for
Thus I proposed specific Regarding the linebreak conversion (from unix to windows): I have no idea, what could cause this.
Thus I have no idea, how these CRLF could end up in the start script. After running Maybe #110 accidentally fixes the lineending issue. But that's just a wild hope ... |
Ugh, I should have guessed ant was being difficult. Thanks for the pointer. However, I applied your patch, but the permissions are still 644 in the freshly built zip. Did it work for you? Similarly, I can not replicate the CRLF behaviour. The file is still in unix format in the zip for me... however my machine is not what is being used to build the nightlies. |
@sumpfralle : Are you experiencing the same issue using the new development build? |
I downloaded the latest nightly build (
freecol-nightly-20220420.zip
).It contained the script
freecol
in the directoryfreecol
.This script had two issues:
chmod +x freecol/freecol
.bash: freecol/freecol: /bin/sh^M: bad interpreter: No such file or directory
^M
marks thecarriage return
(\r
) which is not supposed to be there and which is interpreted as being part of the filenamefromdos freecol/freecol
The original script in the repository looks good:
packaging/common/freecol.sh
(executable flag and correct line ending).Thus I guess, that
build.xml
needs some adjustments.Thank you for your time!
The text was updated successfully, but these errors were encountered: