From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] kernel image size depends on toolchain?
Date: Wed, 11 Jun 2008 23:30:42 +0200 [thread overview]
Message-ID: <200806112330.43075.markus.heidelberg@web.de> (raw)
In-Reply-To: <484F8F05.2040105@gin.de>
Andreas Kuehn, 11.06.2008:
> Is there a chance that something in the uclibc like the LARGEFILESUPPORT
> creates some static or incompressable data block?
The kernel is not being linked against uClibc, so there is no influence.
Markus
next prev parent reply other threads:[~2008-06-11 21:30 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
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 ` Markus Heidelberg [this message]
2008-06-11 8:30 ` [Buildroot] kernel image size depends on toolchain? 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=200806112330.43075.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--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