Vishal,

Thank you for the tips, now I can successfully use the “linaro_android_build_cmds.sh” script and three tar-balls files have been generated.

Regards,

Yanfeng

From: Vishal Bhoj [mailto:vishal.bhoj@linaro.org]
Sent: Monday, November 11, 2013 10:48 AM
To: Yanfeng Liu
Subject: Re: Linaro 13.10 pandaboard built improer use of mkuserimg.sh?

On 11 November 2013 07:49, Yanfeng Liu <Yanfeng.Liu@ygomi.com> wrote:

Vishal,

Thank you for the help, I can make the tar balls by using the targets you named.

BTW, I couldn’t find answers from the build guide page:

· What are the differences between pinned-manifest.xml and pinned-manifest-ann.xml?

pinned-manifest-ann.xml is something we use for adding git descriptions in the file that gets rendered on the release page.

· What valid login/user-id should be provided to “linaro_android_build_cmds.sh” to get the linaro private repo? What are those private repo for?

These private repos are related to member's only private build. Need not worry about it. 

I am using the “pinned-manifest.xml” and I don’t provide the login/user-id to the build script. Even though I can manually build the tar balls, the build script “linaro_android_build_cmds.sh –m pinned-manifest.xml” failed here:

There is a bug in the  linaro_android_build_cmds.sh . Can you please remove this line and it should work well: 

"export TARGET_KERNEL_SOURCE="

echo building kernel uImage with config android_omap4_defconfig for bootloader uboot

building kernel uImage with config android_omap4_defconfig for bootloader uboot

mkdir -p /home/yanfeng/linaro/android/out/target/product/pandaboard/obj/kernel

cp out/target/product/pandaboard/u-boot.img out/target/product/pandaboard/boot

        … …

        make  O=/home/yanfeng/linaro/android/out/target/product/pandaboard/obj/kernel ARCH=arm CROSS_COMPILE=/home/yanfeng/linaro/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro/bin/arm-linux-androideabi- KCFLAGS="-mtune=cortex-a9 -mcpu=cortex-a9 -fno-pic -mno-unaligned-access" LD=$LD uImage

make[1]: warning: -jN forced in submake: disabling jobserver mode.

make[1]: Entering directory `/home/yanfeng'

make[1]: *** No rule to make target `defconfig'.  Stop.

make[1]: Leaving directory `/home/yanfeng'

make: *** [android_kernel] Error 2

make: *** Waiting for unfinished jobs....

The build log is attached with this email for your review.

Regards,

Yanfeng

From: Vishal Bhoj [mailto:vishal.bhoj@linaro.org]
Sent: Friday, November 08, 2013 11:40 PM
To: Yanfeng Liu
Cc: linaro-release@lists.linaro.org
Subject: Re: Linaro 13.10 pandaboard built improer use of mkuserimg.sh?

Hi Yanfeng,

We build the tarballs and not images unlike AOSP. You can build the tarballs using this command:
make userdatatarball systemtarball boottarball.

Installation instruction are available here:
http://releases.linaro.org/13.10/android/panda#tabs-2

Regards,
Vishal

On 8 November 2013 20:59, Yanfeng Liu <Yanfeng.Liu@ygomi.com> wrote:

Hi,

I am not sure if this is the right place to ask for help. Please redirect me if I am wrong here.

I was trying to build the Linaro for Panda board using the latest Linaro 13.10 engineering release with manifest http://releases.linaro.org/13.10/android/panda/pinned-manifest.xml.

The build failed due to an improper usage of "mkuserimg.sh" script like below:

...
make[1]: Leaving directory `/home/yanfeng/linaro/android/external/busybox'
Target system fs image: out/target/product/pandaboard/system.img
Running:  mkuserimg.sh out/target/product/pandaboard/system out/target/product/pandaboard/system.img ext4 system out/target/product/pandaboard/root/file_contexts

This above use of the "mkuserimg.sh" will eventually fail due to the lack of "size" parameter is missing after "ext4".

Hoping someone can give me a pointer about how to fix it.

Regards,
Yanfeng


_______________________________________________
linaro-release mailing list
linaro-release@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-release