linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	celinux-dev@tree.celinuxforum.org
Subject: Re: 2.6.5-rc1-tiny1 for small systems
Date: Wed, 7 Apr 2004 11:40:35 -0500	[thread overview]
Message-ID: <20040407164035.GT6248@waste.org> (raw)
In-Reply-To: <200404070833.26197.vda@port.imtp.ilyichevsk.odessa.ua>

On Wed, Apr 07, 2004 at 08:33:25AM +0300, Denis Vlasenko wrote:
> On Wednesday 17 March 2004 00:25, Matt Mackall wrote:
> > This is the latest release of the -tiny kernel tree. The aim of this
> > tree is to collect patches that reduce kernel disk and memory
> > footprint as well as tools for working on small systems. Target users
> > are things like embedded systems, small or legacy desktop folks, and
> > handhelds.
> >
> > This release is primarily a resync with 2.6.5-rc1 and contains various
> > compile fixes and other cleanups.
> >
> > The patch can be found at:
> >
> >  http://selenic.com/tiny/2.6.5-rc1-tiny1.patch.bz2
> >  http://selenic.com/tiny/2.6.5-rc1-tiny1-broken-out.tar.bz2
> >
> > Webpage for your bookmarking pleasure:
> >
> >  http://selenic.com/tiny-about/
> 
> With attached .config, I get this:
>   CC      lib/div64.o
>   CC      lib/dump_stack.o
>   CC      lib/errno.o
>   CC      lib/extable.o
>   CC      lib/idr.o
>   CC      lib/inflate.o
> lib/inflate.c:138: syntax error before "void"
> make[1]: *** [lib/inflate.o] Error 1
> make: *** [lib] Error 2
> 
> lib/inflate.c:
> static u32 crc_32_tab[256];
> 
> static INIT void makecrc(void)
>        ^^^^
> {
>         unsigned i, j;
>         u32 c = 1;

Just changing that to __init should fix things. That got broken in a
recent patch reordering and doesn't get compiled with the CRC
shrinking option on.

> Originally I wanted to have CONFIG_MEASURE_INLINES=y,
> but it died even earlier, looks like my gcc does not like
> the fact that there is way too many warnings for
> eisa-bus.c.

Hmm, that's interesting. The measure inlines stuff works by generating
warnings, but I have yet to see recent GCC quit after too many warnings.

-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

  reply	other threads:[~2004-04-07 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 22:25 2.6.5-rc1-tiny1 for small systems Matt Mackall
2004-04-07  5:33 ` Denis Vlasenko
2004-04-07 16:40   ` Matt Mackall [this message]
2004-04-07 18:11     ` Denis Vlasenko
     [not found]       ` <200404082142.28409.vda@port.imtp.ilyichevsk.odessa.ua>
2004-04-08 18:52         ` Matt Mackall

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=20040407164035.GT6248@waste.org \
    --to=mpm@selenic.com \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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;
as well as URLs for NNTP newsgroup(s).