From: Risto Pajula <risto@wapice.com>
To: openembedded-devel@lists.openembedded.org
Subject: large uImage size
Date: Sun, 13 Jan 2008 17:18:55 +0200 [thread overview]
Message-ID: <200801131718.55872.risto@wapice.com> (raw)
Hello.
I am getting very large kernel image size (~4,5 MB) when using the
cross-compiler built with a recent version of openembedded. Normal kernel
image size is around 1,5 MB. The large kernel image size only happens when
building the kernel outside the openembedded build environment, when building
with the normal OE build (bitbake minimal-image) the resulting kernel image
size is normal.
This has however changed in some point of OE development. If I use an old OE
snapshot and build the crosscompiler with it the resulting kernel image even
when building outside OE environment is normal. (Both however use gcc 4.1.2).
I have tried to figure what is different in the environment when building the
kernel within OE and outside it but any of the environment variables and etc.
have not solved the problem.
Does anybody know any changes in the OE which could cause this different
behaviour in the gcc cross-compiler built with it?
Machine: at91sam9263-ek.
The kernel compilation ouside OE:
make ARCH=arm
CROSS_COMPILE=/PATH_TO_OE_BUILD_DIR/tmp/cross/bin/arm-angstrom-linux-gnueabi-
uImage
I want to build the development kernel outside of openembedded framewok for
various reasons but use OE crosscompiler. So any help or suggestions for
figuring out why this happens would be appreciated.
BR.
Risto
next reply other threads:[~2008-01-13 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 15:18 Risto Pajula [this message]
2008-01-13 15:33 ` large uImage size Philip Balister
2008-03-14 22:12 ` Tom Rini
2008-01-13 15:35 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801131718.55872.risto@wapice.com \
--to=risto@wapice.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.