All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: large uImage size
Date: Sun, 13 Jan 2008 16:35:52 +0100	[thread overview]
Message-ID: <478A2FD8.5060103@student.utwente.nl> (raw)
In-Reply-To: <200801131718.55872.risto@wapice.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Risto Pajula schreef:
| 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?

http://www.openembedded.org/repo/org.openembedded.dev/packages/linux/linux-2.6.23/binutils-buildid-arm.patch

|
| 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

any valid reasons?


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHii/YMkyGM64RGpERAnUCAJ9SiBslj6zIdKOC1v8FapxmyPNi+gCgqJDP
zLSyPC/dzhhoh3KULKcA/Hw=
=V0yR
-----END PGP SIGNATURE-----



      parent reply	other threads:[~2008-01-13 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 15:18 large uImage size Risto Pajula
2008-01-13 15:33 ` Philip Balister
2008-03-14 22:12   ` Tom Rini
2008-01-13 15:35 ` Koen Kooi [this message]

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=478A2FD8.5060103@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.