Hi everyone.
I've setup a set of builds to examine how my BUILD-INFO.txt overlays are
interpreted by the build system.
Sadly the tests seem to indicate that the system does not work. There
are two tests to show this:
Build:
https://android-build.linaro.org/builds/~zkrynicki/origen-ics-gcc47-samsung…
This build uses:
1) Samsung 'name' of the build
2) Panda source code
3) Fake overlay with snowball license
The result is: samsung license presented.
Build:
https://android-build.linaro.org/builds/~zkrynicki/origen-ics-gcc47-samsung…
Points 1-3 as before, the only difference is some switch in jenkins
(that I cannot see as I don't have access to jenkins) that instructs it
to pull BUILD-INFO.txt from the build tree.
The result is: no license is presented, any file can be downloaded at will
Both builds are correct in the term that BUILD-INFO.txt is copied to the
output directory, alongside system.tar.bz2 This can be easily confirmed
by grepping for BUILD-INFO.txt in the full build logs
My suggestion for tomorrow:
1) I'd like to work with Gesha who implemented the php based system to
debug why build #6 failed to work.
Gesha: would you have some time to work on this (in sync) tomorrow?
2) I'd like to get it to work as intended. Getting access to jenkins
would make this part much much easier (I suspect that requires
danilos/asac to ack).
3) I'd like to ACK the plan on how to switch production builds to this
with all the stakeholders (asac, pfefferz, gesha).
Currently we are in position to switch everything bug samsung/origen
builds (still waiting for a response from anyone on the samsung team,
will reiterate/escalate to get response and move the topic). The only
things that are preventing us from doing this is the actual
build/download system integration.
Thanks everyone.
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Hey everyone,
So we put a hack in (that I fully endorsed) to allow us to easily
switch between builds that have hardware acceleration and those that
don't.
We pass
TARGET_NO_HARDWAREGFX=1
We also have a hack that allows us to easily switch the kernel config:
KERNEL_CONFIG=omap4plus_defconfig
If you see these in a build you're trying to recreate locally, please
export these variables.
We did this to cut down on build variants, but we're going to revisit
things soon.
:)
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
I've ported git://android.git.linaro.org/platform/hardware/linaro/tinyhal.git
to JellyBean - but somehow, the commit appears to get "forgotten"
about. At first I thought I forgot to commit, but the port patch keeps
disappearing.
Since nobody has screamed at me, I don't think my patch broke anything
causing it to be reverted.
By any chance, is tinyhal being mirrored from git.linaro.org, killing
off any changes made on android.git.linaro.org?
ttyl
bero
Botao, Amit: Here are the builds we'll be looking at for the 12.07 android
release. Please boot test them as soon as possible, and respond with the
results. Once they are good, David will tag and rebuild them in the
-release branch, and respond with the new URLs. We'll then need to pick up
the new builds from those URLs and do the rest of the testing on them.
Please take this opportunity to also double-check the gcc version that was
used to build the kernel and make sure it's the 12.07 release of gcc.
Panda:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-til…
- Boot test on both 4430 and 4460
Snowball:
https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-…
- Please check glmark2, it failed in the lava tests, but looks like it
was due to a networking glitch with linaro-android-test not detecting the
network in time. If this looks bad in the boot test, revert to build 369
and boot test it.
Origen:
https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc47-sa…
- Please check glmark2 on this one too. If this one doesn't look good,
revert to build 88
Vexpress-a9:
https://android-build.linaro.org/builds/~linaro-android/vexpress-ics-gcc47-…
Ryan/Tixy are testing the vexpress-tc2 release. Could one of you please
respond with the build URL? I couldn't seem to locate it. Also, after boot
testing, Zach may want it to be rebuilt in a -release branch. I'll defer
to him on that.
Thanks,
Paul Larson
Hi,
i am trying to compile linaro build ( panda-ics-gcc47-tilt-tracking-blob )
on ubuntu 12.04 machine.
The steps and other details.
1. i am using ubuntu 12.04 on intel 64 bit machine.
2. downloaded the latest source code.
3. install gcc-4.7.
4. download the latest tool chain.
5. i followed all the steps mentioned by you.
i am continuously getting the below error code.
/usr/bin/ld: cannot find -lstdc++
/usr/bin/ld: cannot find -lgcc_s
/usr/bin/ld: skipping incompatible
/usr/gcc_4_7/lib/gcc/x86_64-linux-gnu/4.7.2/libgcc.a when searching for
-lgcc
/usr/bin/ld: cannot find -lgcc
collect2: error: ld returned 1 exit status
pleas let me know which linux or other configuration should i use to easily
compile linaro android source code.
what is the easiest way to do that.
regards and thanks
Amit Kumar
Dear Sir or Madam,
At the website https://wiki.linaro.org/Platform/Android/ImageInstallation
What is the difference between quickstart section and Intro section? Those part suppose to do different thing or the same?
What is the pre-built image? Is that the image for kernel?
At the website
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-til…
I can't automatically build the source via script, it tells me I don't have a pinned-manifest.xml.
And where can I find the download button mentioned in "How to Use Prebuilt Images".
When I follow the instructions to compile the Android source code, when it comes to compile kernel/drivers/usb/musb/tusb6010_omap.c it always terminate because of lack of mach/mux.h file.
Please help me.
Best wishes,
Shawn