Thanks Bernhard for the insight.

Yes, it seems that the compiler we use is different than the one used in the Linaro AOSP ICS builds.
We had downloaded toolchain from http://www.linaro.org/downloads/1207 : Toolchains section.

Somehow the cross compiler in the build is arm-linux-gnueabi-gcc(Linaro GCC 4.6) while one we use is arm-eabi-gcc(Linaro GCC 4.7).
I hoping I will find correct version as above and manage to build with it.

I probably should also check whether any compiler flags are set differently.
I am just following the http://source.android.com build process.

BR
Sagar

On 7 October 2012 14:47, Bernhard Rosenkränzer <bernhard.rosenkranzer@linaro.org> wrote:
Hi,

On 6 October 2012 00:01, Sagar Shinde <sangi.hs@gmail.com> wrote:
> Thanksalot for quick response Alexander.
> I did use the same config file mentioned in Linaro AOSP build page.
> I am now pondering whether to check the AOSP ICS sources used by
> Linaro...but usb-ethernet speed related stuff shouldnot be affected by
> anything in framework/userspace.... I use iperf to measure network
> throughput .
> Hence again I suspect kernel changes

There is no difference between the kernel sources. However, they're
potentially built with different compilers and compiler flags.

AOSP uses a prebuilt binary for the kernel, so it's a bit hard to tell
how it was built.
Linaro Android builds the kernel as part of the OS build process, so
it uses whatever compiler flags we're setting for the target.

ttyl
bero