Skip to content

command not found error #5

Open
@Stivius

Description

@Stivius

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions