Android Android compile issue happened

  Thread Rating:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
HenryFord Offline
Posting Freak
Posts: 1,000
Joined: Jan 2010
Reputation: 14
Post: #11
For anyone running into this problem, I was able to solve it by editing the makefiles (at least I think I solved it since it is still compiling (I only ran a single job)):
1. Makefile
2. Makefile.in
3. Makefile.include

In files 1 & 2 I replaced "gettext-native" with "gettext" (the BuildTools line).
In file 3 I edited the path for "XBMCPREFIX", because it included a double-slash. So I changed it from
Code:
=/opt/xbmc_android/android-toolchain/android-9//staging
to
Code:
=/opt/xbmc_android/android-toolchain/android-9/staging

I suspect that that is the reasons for the build failing rather then replacing "gettext-native" with "gettext".

Need help? Check out my XBMC Eden Guide. It contains full featured guides to Sickbeard and CouchPotato as well.

[Image: all-fanart.jpg]
(This post was last modified: 2012-08-01 11:54 by HenryFord.)
find quote
denisyq Offline
Junior Member
Posts: 6
Joined: Jul 2012
Reputation: 0
Post: #12
(2012-07-31 16:12)Memphiz Wrote:  And you are definitly using the crystax NDK? And you are sure that make -j20 in depends got through the first time? (sometimes it has issues with parallel build which leads to uncomplete built dependencies). It should have stated something like "All Dependencies built successfully" or so.

yeah, i am definitely using the crystax NDK as the guide said. but i did not get the "All Dependencies built successfully " statements as i run make -j20.
NO errors shows after make -j20 and i suppose it is all right.
does my version of ubuntu (10.04) make any effort?
find quote
HenryFord Offline
Posting Freak
Posts: 1,000
Joined: Jan 2010
Reputation: 14
Post: #13
(2012-08-01 14:04)denisyq Wrote:  NO errors shows after make -j20 and i suppose it is all right.
That is to be expected - since you run it in 20 jobs, the probability is high that you'll miss the errors a long the build.
Try running with a single job, you then can see the errors.
I suspect that the dependencies in your case didn't build all the way through (just like my case).

For reference:
I had another problem with the compilation as "afpfs-ng" was being built. The output told me that "rm" and "mkdir" are missing. I changed the PATH-value in the makefile and added my /bin folder to it. It's still running at this point, so I hope it'll complete this time around (again - only one job does make things slooooooooooow)

Edit:
So, my dependencies went through fine as it seems. XBMC is compiling right now, bootstrap and configure were successfull.
Sidenote:
I had to manually install "gperf" on my system since it wasn't installed, but was expected to be there. Installing it solved the problem and as said - the compilation runs now. Will add if I was able to successfully build the apk.

Need help? Check out my XBMC Eden Guide. It contains full featured guides to Sickbeard and CouchPotato as well.

[Image: all-fanart.jpg]
(This post was last modified: 2012-08-01 16:15 by HenryFord.)
find quote
denisyq Offline
Junior Member
Posts: 6
Joined: Jul 2012
Reputation: 0
Post: #14
(2012-08-01 11:54)HenryFord Wrote:  For anyone running into this problem, I was able to solve it by editing the makefiles (at least I think I solved it since it is still compiling (I only ran a single job)):
1. Makefile
2. Makefile.in
3. Makefile.include

In files 1 & 2 I replaced "gettext-native" with "gettext" (the BuildTools line).
In file 3 I edited the path for "XBMCPREFIX", because it included a double-slash. So I changed it from
Code:
=/opt/xbmc_android/android-toolchain/android-9//staging
to
Code:
=/opt/xbmc_android/android-toolchain/android-9/staging

I suspect that that is the reasons for the build failing rather then replacing "gettext-native" with "gettext".

I use android-14 for the toolchain and the original makefile/makefile.in/makefile.include is found as the same as yours (after modified). So i suppose it is not the issue. CoolCool
find quote
HenryFord Offline
Posting Freak
Posts: 1,000
Joined: Jan 2010
Reputation: 14
Post: #15
Did you try with a single job in order to actually see error messages when they pop up?

My build just completed successfully...

Need help? Check out my XBMC Eden Guide. It contains full featured guides to Sickbeard and CouchPotato as well.

[Image: all-fanart.jpg]
find quote
denisyq Offline
Junior Member
Posts: 6
Joined: Jul 2012
Reputation: 0
Post: #16
(2012-08-02 10:11)HenryFord Wrote:  Did you try with a single job in order to actually see error messages when they pop up?

My build just completed successfully...

yeah, i did it just a moment ago. I got
Code:
make[3]: Leaving directory `/home/luyanqing/xbmc-android/tools/android/depends/libiconv/armeabi-v7a/man'
make[2]: Leaving directory `/home/luyanqing/xbmc-android/tools/android/depends/libiconv/armeabi-v7a'
touch .installed-armeabi-v7a
make[1]: Leaving directory `/home/luyanqing/xbmc-android/tools/android/depends/libiconv'
make -C gettext
make[1]: Entering directory `/home/luyanqing/xbmc-android/tools/android/depends/gettext'
rm -rf armeabi-v7a/*; mkdir -p armeabi-v7a
/bin/tar -C armeabi-v7a --strip-components=1 -xf /home/luyanqing/xbmc-android/gettext-0.18.1.1.tar.gz

gzip: stdin: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
make[1]: *** [armeabi-v7a] Error 2
make[1]: Leaving directory `/home/luyanqing/xbmc-android/tools/android/depends/gettext'
make: *** [gettext] Error 2
find quote
Montellese Online
Team-XBMC Developer
Posts: 2,789
Joined: Jan 2009
Reputation: 20
Location: Switzerland
Post: #17
Looks like there was a problem when downloading the gettext tarball. Just delete /home/luyanqing/xbmc-android/gettext-0.18.1.1.tar.gz and re-run make on the dependencies.

Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.

[Image: badge.gif]
find quote
denisyq Offline
Junior Member
Posts: 6
Joined: Jul 2012
Reputation: 0
Post: #18
(2012-08-02 11:42)Montellese Wrote:  Looks like there was a problem when downloading the gettext tarball. Just delete /home/luyanqing/xbmc-android/gettext-0.18.1.1.tar.gz and re-run make on the dependencies.

per Montelese's suggestion, i delete the gettext tarball and re-run make (it will download the tarball automatically). It seems that helped.
I could compile successfully but have to face another issue about apk make.
I got to say the version of UBUNTU should be newer than 10.
find quote
davilla Offline
Team-XBMC Developer
Posts: 10,399
Joined: Feb 2008
Reputation: 58
Post: #19
To quote README.android



-----------------------------------------------------------------------------
1. Introduction
-----------------------------------------------------------------------------

We currently recommend Ubuntu Natty (11.04) or later. Current work has been
done here. Additionally, building from OSX Snow Leopard is working.


buiilding on anything else is unsupported at the current time.


MediaInfo : http://mediainfo.sourceforge.net/
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
find quote
Memphiz Offline
Team-XBMC Developer
Posts: 7,677
Joined: Feb 2011
Reputation: 91
Location: germany
Post: #20
I've build successfully on 10.04 *whistles*

AppleTV2/iPhone/iPod: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for XBMC: Wiki NFS
HowTo configure avahi (zeroconf): Wiki Avahi
READ THE IOS FAQ!: iOS FAQ
find quote
Post Reply