From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] kernel image size depends on toolchain?
Date: Wed, 11 Jun 2008 11:31:02 +0200 [thread overview]
Message-ID: <87lk1cmi7d.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <484F8F05.2040105@gin.de> (Andreas Kuehn's message of "Wed\, 11 Jun 2008 10\:38\:29 +0200")
>>>>> "Andreas" == Andreas Kuehn <Andreas.Kuehn@gin.de> writes:
Hi,
Andreas> That is how I found that thing. It simply doesn't fit into my boot
Andreas> flash anymore.
Andreas> And Yes, it is the same, not even a copy, .config file for both trys.
Andreas> The reason why I need the "new" uclibc is, that I need access to the
Andreas> PIOs of my at91sam9261 and at91sam9263 controllers. And the "old"
Andreas> uclibc has this mmap bug that creates an page overflow error.
Andreas> Is there a chance that something in the uclibc like the
Andreas> LARGEFILESUPPORT creates some static or incompressable data block?
That doesn't sound likely. Are the vmlinux files also different in
sizes? Try comparing output of $CROSS-nm on the vmlinux files.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-06-11 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 7:40 [Buildroot] kernel image size depends on toolchain? Andreas Kuehn
2008-06-11 7:55 ` Peter Korsgaard
2008-06-11 8:38 ` Andreas Kuehn
2008-06-11 9:31 ` Peter Korsgaard [this message]
2008-06-11 10:20 ` Andreas Kuehn
2008-06-11 11:09 ` Peter Korsgaard
2008-06-11 13:00 ` Andreas Kuehn
2008-06-11 13:58 ` Peter Korsgaard
2008-06-11 15:08 ` [Buildroot] kernel image size depends on toolchain? -Solved- Andreas Kuehn
2008-06-11 19:24 ` Peter Korsgaard
2008-06-11 21:30 ` [Buildroot] kernel image size depends on toolchain? Markus Heidelberg
2008-06-11 8:30 ` Matthew Dombroski
2008-06-11 8:49 ` Andreas Kuehn
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=87lk1cmi7d.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox