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

command not found error #5

Open
Stivius opened this issue Jan 5, 2021 · 1 comment
Open

command not found error #5

Stivius opened this issue Jan 5, 2021 · 1 comment

Comments

@Stivius
Copy link
Contributor

Stivius commented Jan 5, 2021

Since the #4 has been merged I sometimes receive the following error during build:

[gstreamer/stderr] /home/stivius/linuxdeploy-plugin-gstreamer.sh: line 110: : command not found

It completes successfully on my local machine despite these errors but fails in GitHub actions for some reason.
I'm not an expert in bash, but I did some research on this topic.
set -e means exit immediately if a command exits with a non-zero status
grep -v means select non-matching lines
grep --help tells us exit status is 0 if any line is selected, 1 otherwise

And we have the following line 110 in the script:
"$(file "$i" | grep -v ELF --silent)" which means that if ELF is found grep will return 0 I suppose.
Could it be the root problem which causes the script to fail?

@emericg
Copy link

emericg commented Jun 20, 2021

I see that error too. Doesn't appear to be blocking anything, but still, prints a lot of messages to stderr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants