Skip to content
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

config.guess error #2668

Closed
kongdd opened this issue Jul 19, 2018 · 4 comments
Closed

config.guess error #2668

kongdd opened this issue Jul 19, 2018 · 4 comments
Labels
help wanted Help is wanted in order to solve the issue. packaging Issue related to building packages, not affecting end users directly.

Comments

@kongdd
Copy link

kongdd commented Jul 19, 2018

I am using the latest termux-packages and its corresponding docker. An error occur.

PS D:\termux-packages> ./scripts/run-docker.ps1 ./build-package.sh libandroid-support
Running container termux-package-builder from image termux/package-builder...
termux-package-builder
: not founder/termux-packages/scripts/config.guess: 4: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 6: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 33: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 34: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 36: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 48: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 57: /home/builder/termux-packages/scripts/config.guess:
: not founder/termux-packages/scripts/config.guess: 60: /home/builder/termux-packages/scripts/config.guess:
/home/builder/termux-packages/scripts/config.guess: 63: /home/builder/termux-packages/scripts/config.guess: Syntax error
: word unexpected (expecting "in")
@Grimler91 Grimler91 added the packaging Issue related to building packages, not affecting end users directly. label Aug 17, 2018
@fornwall fornwall added the help wanted Help is wanted in order to solve the issue. label Aug 27, 2018
@fornwall
Copy link
Member

Is this windows-specific? Anyone on windows who can help out?

@AgentConDier
Copy link
Contributor

AgentConDier commented Apr 25, 2019

I changed the shebang to bash and enforced unix-style line endings with notepad++, not sure which of those did it but it works now. Now I've got an error with python3\r not being found, but that is easily fixable. I think this may be caused by git-bash's setting core.autocrlf to automatically convert all line endings to the platform you're on.

@Mipsters
Copy link

Mipsters commented May 23, 2020

sorry to wake this up, but I just had the same problem and it was the line ending
and @AgentConDier , can you share how you fixed the python3\r problem?

edit: found the problem
the file scripts/buildorder.py had windows style line ending, so the shebang was #!/usr/bin/env python3\r

edit 2: it seems like this problem is happening in a few other places, maybe its a good idea to force this repo clone to have unix line ending, because it uses docker heavily
this may be possible to achieve with .gitattributes

ghost pushed a commit that referenced this issue May 23, 2020
@ghost
Copy link

ghost commented May 23, 2020

@Mipsters gitattributes fixed in aac32ad.

Files should now have LF endings, except the run-docker.ps1.

@ghost ghost closed this as completed May 23, 2020
@termux termux locked and limited conversation to collaborators Oct 9, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Help is wanted in order to solve the issue. packaging Issue related to building packages, not affecting end users directly.
Projects
None yet
Development

No branches or pull requests

5 participants