{"action":"created","issue":{"url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/6","repository_url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android","labels_url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/6/comments","events_url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/6/events","html_url":"https://github.com/happyalu/Flite-TTS-Engine-for-Android/issues/6","id":1149455,"number":6,"title":"Build Instructions","user":{"login":"austintino","id":886786,"avatar_url":"https://avatars.githubusercontent.com/u/886786?v=3","gravatar_id":"","url":"https://api.github.com/users/austintino","html_url":"https://github.com/austintino","followers_url":"https://api.github.com/users/austintino/followers","following_url":"https://api.github.com/users/austintino/following{/other_user}","gists_url":"https://api.github.com/users/austintino/gists{/gist_id}","starred_url":"https://api.github.com/users/austintino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/austintino/subscriptions","organizations_url":"https://api.github.com/users/austintino/orgs","repos_url":"https://api.github.com/users/austintino/repos","events_url":"https://api.github.com/users/austintino/events{/privacy}","received_events_url":"https://api.github.com/users/austintino/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2011-07-01T09:07:19Z","updated_at":"2016-02-11T10:27:33Z","closed_at":"2012-03-11T13:48:44Z","body":"The build instructions are a bit vague as to which directories you should be in when carrying out the steps.\r\n\r\nIs it possible to post a slightly more detailed version for v1.0.0-RC3?\r\n\r\nCheers,\r\nb "},"comment":{"url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/comments/182795198","html_url":"https://github.com/happyalu/Flite-TTS-Engine-for-Android/issues/6#issuecomment-182795198","issue_url":"https://api.github.com/repos/happyalu/Flite-TTS-Engine-for-Android/issues/6","id":182795198,"user":{"login":"nand4614355","id":8537638,"avatar_url":"https://avatars.githubusercontent.com/u/8537638?v=3","gravatar_id":"","url":"https://api.github.com/users/nand4614355","html_url":"https://github.com/nand4614355","followers_url":"https://api.github.com/users/nand4614355/followers","following_url":"https://api.github.com/users/nand4614355/following{/other_user}","gists_url":"https://api.github.com/users/nand4614355/gists{/gist_id}","starred_url":"https://api.github.com/users/nand4614355/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nand4614355/subscriptions","organizations_url":"https://api.github.com/users/nand4614355/orgs","repos_url":"https://api.github.com/users/nand4614355/repos","events_url":"https://api.github.com/users/nand4614355/events{/privacy}","received_events_url":"https://api.github.com/users/nand4614355/received_events","type":"User","site_admin":false},"created_at":"2016-02-11T10:27:32Z","updated_at":"2016-02-11T10:27:32Z","body":"configure: error: cannot guess build type; you must specify one\n\n\nOn Thu, Feb 11, 2016 at 2:00 PM, Alok Parlikar <notifications@github.com>\nwrote:\n\n> Not sure how \"--build=x86\" is impacting this. What happens when you try \"\n>\n> ./configure --with-langvox=android --target=armeabiv7a-android\n>\n>\n> On Thu, Feb 11, 2016 at 11:25 AM, nand4614355 <notifications@github.com>\n> wrote:\n>\n>\n> > Getting same error. Here is configure output\n> >\n> > ./configure --with-langvox=android --target=armeabiv7a-android\n> --build=x86\n> > checking build system type... x86-unknown-none\n> > checking host system type... x86-unknown-none\n> > checking target system type... armeabiv7a-unknown-android\n> > checking for gcc... gcc\n> > checking whether the C compiler works... yes\n> > checking for C compiler default output file name... a.exe\n> > checking for suffix of executables... .exe\n> > checking whether we are cross compiling... no\n> > checking for suffix of object files... o\n> > checking whether we are using the GNU C compiler... yes\n> > checking whether gcc accepts -g... yes\n> > checking for gcc option to accept ISO C89... none needed\n> > checking for ranlib... ranlib\n> > checking for a BSD-compatible install... /usr/bin/install -c\n> > checking for ar... ar\n> > checking how to run the C preprocessor... gcc -E\n> > checking for grep that handles long lines and -e... /usr/bin/grep\n> > checking for egrep... /usr/bin/grep -E\n> > checking for ANSI C header files... yes\n> > checking for sys/types.h... yes\n> > checking for sys/stat.h... yes\n> > checking for stdlib.h... yes\n> > checking for string.h... yes\n> > checking for memory.h... yes\n> > checking for strings.h... yes\n> > checking for inttypes.h... yes\n> > checking for stdint.h... yes\n> > checking for unistd.h... yes\n> > checking whether byte ordering is bigendian... no\n> > checking for mmap... no\n> > checking sys/soundcard.h usability... no\n> > checking sys/soundcard.h presence... yes\n> > configure: WARNING: sys/soundcard.h: present but cannot be compiled\n> > configure: WARNING: sys/soundcard.h: check for missing prerequisite\n> > headers?\n> > configure: WARNING: sys/soundcard.h: see the Autoconf documentation\n> > configure: WARNING: sys/soundcard.h: section \"Present But Cannot Be\n> > Compiled\"\n> > configure: WARNING: sys/soundcard.h: proceeding with the compiler's\n> result\n> > checking for sys/soundcard.h... no\n> > checking machine/soundcard.h usability... no\n> > checking machine/soundcard.h presence... no\n> > checking for machine/soundcard.h... no\n> > checking sys/audioio.h usability... no\n> > checking sys/audioio.h presence... no\n> > checking for sys/audioio.h... no\n> > checking mmsystem.h usability... no\n> > checking mmsystem.h presence... yes\n> > configure: WARNING: mmsystem.h: present but cannot be compiled\n> > configure: WARNING: mmsystem.h: check for missing prerequisite headers?\n> > configure: WARNING: mmsystem.h: see the Autoconf documentation\n> > configure: WARNING: mmsystem.h: section \"Present But Cannot Be Compiled\"\n> > configure: WARNING: mmsystem.h: proceeding with the compiler's result\n> > checking for mmsystem.h... no\n> > configure: creating ./config.status\n> > config.status: creating config/config\n> > config.status: creating config/system.mak\n> >\n> >\n> > On Wed, Feb 10, 2016 at 5:52 PM, Alok Parlikar <notifications@github.com\n> >\n> > wrote:\n> >\n> > > make[2]:\n> > >\n> >\n> C:\\Users\\h149056\\Downloads\\android-ndk-r10e/toolchains/x86-4.6/prebuilt/linux-x86/bin/i686-linux-android-gcc:\n> > > Command not found\n> > >\n> > > Please edit the \"configure\" file to the correct GCC location on your\n> > > system. That should resolve this.\n> > >\n> > > —\n> > > Reply to this email directly or view it on GitHub\n> > > <\n> >\n> https://github.com/happyalu/Flite-TTS-Engine-for-Android/issues/6#issuecomment-182344809\n> > >\n> > > .\n> >\n> > >\n> >\n> > —\n> > Reply to this email directly or view it on GitHub\n> > <\n> https://github.com/happyalu/Flite-TTS-Engine-for-Android/issues/6#issuecomment-182730460\n> >\n>\n> > .\n> >\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/happyalu/Flite-TTS-Engine-for-Android/issues/6#issuecomment-182761623>\n> .\n>\n"}}