[Android] [fixed] VisualGDB error

Sysprogs forums Forums VisualGDB [Android] [fixed] VisualGDB error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #496
    cdoty
    Participant

    I get the following error when trying to build the example project (New app with sample native library) under Visual Studio 2008 on 32 bit Windows 7:

    1>

    Build started: Project: AndroidApp1, Configuration: Debug Win32

    1>Performing Makefile project actions
    1>Gdbserver : [arm-linux-androideabi-4.4.3] libs/armeabi/gdbserver
    1>/usr/bin/sh: -c: line 1: syntax error: unexpected end of file
    1>make: *** [c:/AppDev/AndroidApp1//libs/armeabi/gdbserver] Error 1
    1>Project : error PRJ0019: A tool returned an error code from “Performing Makefile project actions”

    I tried the build command on the command line and I get the same error.

    #2228
    support
    Keymaster

    Hi,
    This happens due to a PATH conflict with another GNU-based toolchain on your computer (such as WinAVR).

    When Android tools are invoked, a wrong version of sh.exe gets executed and it breaks down the compilation.
    Please remove all directories that can contain sh.exe and similar tools from the PATH variable before starting Visual Studio. Note that you might need to restart your computer after modfying the PATH variable in system settings.

    #2231
    support
    Keymaster

    The PATH bug has been fixed in VisualGDB 2.1. Please also use NDK r8 or newer.

    #2229
    Anonymous
    Participant

    Hi,

    I’ve this error :
    1>C:androidandroid-ndk-r7bndk-build.cmd NDK_DEBUG=1 APP_PLATFORM=android-8
    1>Gdbserver : [arm-linux-androideabi-4.4.3] libs/armeabi/gdbserver
    1>/usr/bin/sh: -c: line 1: syntax error: unexpected end of file
    1>make: *** [c:/src/vgdb/android1/android1//libs/armeabi/gdbserver] Error 1

    I’m using VisualGDB version 2.2

    I’m a Window7 user (PC 32Bits)

    I’ve just one version of SH.EXE (536078 KB).

    What must I do exactly?

    #2230
    support
    Keymaster

    Please do the following:
    1. Install VisualGDB 2.3 or later.
    2. Install Android NDK r8 or later

    Android NDK r8 fixes the bug by adding SHELL=cmd to the ndk-build.cmd file.
    You can alternatively get a fixed ndk-build.cmd file from here: http://visualgdb.com/KB/ndk-build.zip

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.