bin/bash: i: command not found when building Gstreamer example 5 on Android Studio

[Martin Kelly]

On 04/11/2016 07:08 AM, Vincenzo Di Giovambattista wrote:
>
> The Gradle Console is showing several
>
> |/bin/bash: i: command not found make: [genstatic_armeabi] Error 127
> (ignored) |
>
> Here below the complete Console log:
>
> |bin/bash: - : invalid option Usage: /bin/bash [GNU long option] [option]
> ... /bin/bash [GNU long option] [option] script-file ... GNU long
> options: --debug --debugger --dump-po-strings --dump-strings --help
> --init-file --login --noediting --noprofile --norc --posix --protected
> --rcfile --restricted --verbose --version --wordexp Shell options: -irsD
> or -c command or -O shopt_option (invocation only) -abefhkmnptuvxBCHP or
> -o option /bin/bash: - : invalid option Usage: /bin/bash [GNU long
> option] [option] ... /bin/bash [GNU long option] [option] script-file
> ... GNU long options: --debug --debugger --dump-po-strings
> --dump-strings --help --init-file --login --noediting --noprofile --norc
> --posix --protected --rcfile --restricted --verbose --version --wordexp
> ...... GStreamer : [GEN] => gst-build-armeabi/gstreamer_android.c
> /bin/bash: i: command not found make: [genstatic_armeabi] Error 127
> (ignored) /bin/bash: i: command not found make: [genstatic_armeabi]
> Error 127 (ignored) /bin/bash: i: command not found make:
> [genstatic_armeabi] Error 127 (ignored) /bin/bash: i: command not found
> make: [genstatic_armeabi] Error 127 (ignored) GStreamer : [COMPILE] =>
> gst-build-armeabi/gstreamer_android.c
> gst-build-armeabi/gstreamer_android.c:17:2: error: stray '@' in program
> @PLUGINS_DECLARATION@ ^ gst-build-armeabi/gstreamer_android.c:17:22:
> error: stray '@' in program @PLUGINS_DECLARATION@ ^
> gst-build-armeabi/gstreamer_android.c:20:2: error: stray '@' in program
> @G_IO_MODULES_DECLARE@ ^ gst-build-armeabi/gstreamer_android.c:17:3:
> error: unknown type name 'PLUGINS_DECLARATION' @PLUGINS_DECLARATION@ ^
> gst-build-armeabi/gstreamer_android.c:20:23: error: stray '@' in program
> @G_IO_MODULES_DECLARE@ ^ gst-build-armeabi/gstreamer_android.c:23:1:
> error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
> void ^ gst-build-armeabi/gstreamer_android.c:26:2: error: stray '@' in
> program @PLUGINS_REGISTRATION@ ^
> gst-build-armeabi/gstreamer_android.c:26:23: error: stray '@' in program
> @PLUGINS_REGISTRATION@ ^ gst-build-armeabi/gstreamer_android.c: In
> function 'gst_android_load_gio_modules':
> gst-build-armeabi/gstreamer_android.c:33:2: error: stray '@' in program
> @G_IO_MODULES_LOAD@ ^ gst-build-armeabi/gstreamer_android.c:33:20:
> error: stray '@' in program @G_IO_MODULES_LOAD@ ^
> gst-build-armeabi/gstreamer_android.c:33:3: error: 'G_IO_MODULES_LOAD'
> undeclared (first use in this function) @G_IO_MODULES_LOAD@ ^
> gst-build-armeabi/gstreamer_android.c:33:3: note: each undeclared
> identifier is reported only once for each function it appears in
> gst-build-armeabi/gstreamer_android.c:34:1: error: expected ';' before
> '}' token } ^ gst-build-armeabi/gstreamer_android.c: In function
> 'gst_android_init': gst-build-armeabi/gstreamer_android.c:497:3: error:
> implicit declaration of function 'gst_android_register_static_plugins'
> [-Werror=implicit-function-declaration]
> gst_android_register_static_plugins (); ^ cc1: all warnings being
> treated as errors make: *** [gst-build-armeabi/gstreamer_android.o]
> Error 1 :app:ndkBuild FAILED FAILURE: Build failed with an exception. *
> What went wrong: Execution failed for task ':app:ndkBuild'. > Process
> 'command
> '/Users/vincenzodigiovambattista/AndroidStudioProjects/android-ndk-r11c/ndk-build''
> finished with non-zero exit value 2 |
>
> Any suggestion?
>
>
> Cheers!
>
>
> Vincenzo
>

This looks a lot like the following bug:

https://bugzilla.gnome.org/show_bug.cgi?id=763999

That bug is fixed in master but it looks like it didn't make it into 
1.8.0 (target milestone is 1.8.1). Assuming my theory is correct, you 
may want to try one of the below options:

- Build a package based on current master (or even current 1.8 branch) 
and try again.
- Just as a quick test, you could also try applying the two patches 
listed in the bug report for bug 763999 to your current package. They 
are small patches, so they will likely apply cleanly, and it could 
quickly show whether or not this really is the issue.