From: Bob Tracy <rct@gherkin.frus.com>
To: Matt Turner <mattst88@gmail.com>
Cc: linux-alpha <linux-alpha@vger.kernel.org>,
Debian Alpha Mailing List <debian-alpha@lists.debian.org>,
Michael Cree <mcree@orcon.net.nz>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [BUG] 4.9.0 build error on Alpha
Date: Thu, 29 Dec 2016 21:37:47 -0600 [thread overview]
Message-ID: <20161230033747.GB26007@gherkin.frus.com> (raw)
In-Reply-To: <CAEdQ38EX1rmir0bbY+S-QMfepyBsUJ1uEUjP3A76z8NF5dyrhA@mail.gmail.com>
On Thu, Dec 29, 2016 at 10:23:04PM -0500, Matt Turner wrote:
> FWIW, when I saw your first email I tried compiling with gcc-4.9.4,
> 5.4.0, and 6.2.0. All compiled my config fine.
That's worth quite a bit to me, actually :-). Tells me that downgrading
my toolchain is probably a waste of time and effort.
> I'm guessing it's another symptom of the old "kernel too big" problem?
How has this been worked around in the past? I have a fairly
feature-full kernel, but the only built-in drivers are for the things
that have to be present at boot time.
If drivers compiled as modules contribute to the bloat, I could easily
omit file system support for things I'll likely never see attached to an
alpha. Similarly, drivers for removable USB devices I don't currently use
with the system could be omitted as well. Netfilter keeps growing like
the hairball it is: features I'm not likely to ever use could be disabled
if that might help.
--Bob
next prev parent reply other threads:[~2016-12-30 3:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 3:08 [BUG] 4.9.0 build error on Alpha Bob Tracy
2016-12-30 3:23 ` Matt Turner
2016-12-30 3:37 ` Bob Tracy [this message]
2016-12-30 16:02 ` Maciej W. Rozycki
2016-12-30 21:07 ` Helge Deller
2016-12-31 6:43 ` Bob Tracy
2016-12-31 7:20 ` Bob Tracy
2016-12-31 10:11 ` Maciej W. Rozycki
2016-12-31 15:20 ` Bob Tracy
2016-12-31 19:38 ` Michael Cree
2016-12-31 21:09 ` Bob Tracy
2017-01-01 1:23 ` Maciej W. Rozycki
2017-01-01 3:32 ` Bob Tracy
2017-01-01 20:29 ` Bob Tracy
2017-01-03 0:15 ` Bob Tracy
2017-01-12 12:52 ` Maciej W. Rozycki
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=20161230033747.GB26007@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=rth@twiddle.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