Linaro Android build(s)

2012-01-29 Thread hedwin
Gents,

For some time now I am trying to build android from the linaro repos.
Sofar I never succedded, it always resulted in build failures or it doesn't
boot.

So what did it do:

I tried the 11.12 release staging and tracking. Got the last to build after
switching to the 4.6 toolchain (nowhere documented) and
added an include to the png.c file (it misted a math.h include, weird).
It only didn't boot correctly because the kernel failed to initialise the
GPU.

So I switched to the 12.01 release. First used the "release-12.01" branch,
build failure. Then switched to the  "linaro_android_4.0.3" branch
Used the same as mentioned in the build service build overview. Also used
the same setup as mentioned in the build service.
Build fails.

Odd thing is that someone must be able to get a successfull build because
ready available images do exist.
So how did these get build? How do I get a good build?

Cheers,
Hedwin


PS, below the build error in the 12.01 release:

workCoreTests_install_verifier_good_intermediates/package.apk)
com.google.doclava.apicheck.ApiParseException: Error parsing API
at
com.google.doclava.apicheck.XmlApiFile.parseApi(XmlApiFile.java:60)
at com.google.doclava.apicheck.ApiCheck.parseApi(ApiCheck.java:152)
at
com.google.doclava.apicheck.ApiCheck.convertToXml(ApiCheck.java:234)
at com.google.doclava.apicheck.ApiCheck.main(ApiCheck.java:64)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.google.doclava.apicheck.XmlApiFile.parseApi(XmlApiFile.java:54)
... 3 more
Error parsing API: frameworks/base/api/current.txt
make: *** [out/target/common/obj/APPS/SignatureTest_intermediates/api.xml]
Error 1
make: *** Waiting for unfinished jobs
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: Linaro Android build(s)

2012-01-29 Thread hedwin
Tony,

thnx for your reply.

Yes followed both instructions, the wiki and the build service.
It is not that I am unfamiliar on how to build android, been doing this
since 2009 when I put android on a TV, this was mips based I now use
omap3530, omap3730 base boards and pandaboard.
The thing is I only cannot get linaro android to build without doing
something specifc. AOSP ICS builds without any issue and runs on my
pandaboard.
I want to use linaro because I think it might be more compleet with respect
to audio and video.

Where it is going wrong for the 12.01 release is (use the linaro 4.6
toolchain and ubunti 11.04):

workCoreTests_install_
verifier_good_intermediates/package.apk)
com.google.doclava.apicheck.ApiParseException: Error parsing API
at
com.google.doclava.apicheck.XmlApiFile.parseApi(XmlApiFile.java:60)
at com.google.doclava.apicheck.ApiCheck.parseApi(ApiCheck.java:152)
at
com.google.doclava.apicheck.ApiCheck.convertToXml(ApiCheck.java:234)
at com.google.doclava.apicheck.ApiCheck.main(ApiCheck.java:64)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.google.doclava.apicheck.XmlApiFile.parseApi(XmlApiFile.java:54)
... 3 more
Error parsing API: frameworks/base/api/current.txt
make: *** [out/target/common/obj/APPS/SignatureTest_intermediates/api.xml]
Error 1
make: *** Waiting for unfinished jobs

Cheers,

Hedwin


On Sun, Jan 29, 2012 at 6:04 PM, Tony Mansson wrote:

> Hi Hedwin.
>
> Have you followed the instructions here?
> https://wiki.linaro.org/Platform/Android
>
> Get the Source Code <https://wiki.linaro.org/Platform/Android/GetSource>
>  and Build the Source 
> Code<https://wiki.linaro.org/Platform/Android/BuildSource> should
> tell you what you need.
>
> The exact details for a board and a release is best checked here:
> https://android-build.linaro.org/
>
> E.g. if you are building the landing-snowball-12.01-release, build number
> 5, you can see which environment and toolchain has been used for this
> build. See below.
>
> Here you can also see that you need to download the toolchain and the
> non-Free binary overlay in vendor.tar.bz2. The instructios are there.
>
> Here's what I do: I put all the environment settings in a shell script and
> source it.
> SOURCE_OVERLAY and
> TOOLCHAIN_URL must point out local directories where you have downloaded
> the overlay and the toolchain. You should remove the LAVA_SUBMIT settings.
>
> Then I go:
> repo init -u ${MANIFEST_REPO} -b ${MANIFEST_BRANCH} -m ${MANIFEST_FILENAME}
> repo sync
> and then perhaps . ./build/envsetup.sh (not necessary for a normal build)
> the build command can look like:
> make -j4 TARGET_PRODUCT=snowball HOST_CC=gcc-4.5 HOST_CXX=g++-4.5
> HOST_CPP=cpp-4.5 boottarball systemtarball userdatatarball showcommands
>
> The HOST_C<*> settings are needed in Ubuntu 11.10 only.
>
> For a Pandaboard you replace "snowball" with "pandaboard" in various
> places.
>
> PLease let us know where we failed to show you what you had missed so we
> can improve our information.
>
> BR,
> Tony
>
>
>
>
> Configuration
>
> MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git
> MANIFEST_BRANCH=linaro-android-12.01-release
> MANIFEST_FILENAME=landing-snowball.xml 
> <http://android.git.linaro.org/platform/manifest.gitMANIFEST_BRANCH=linaro-android-12.01-releaseMANIFEST_FILENAME=landing-snowball.xml>
> TARGET_P