All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc1-mm2 kernel oops
Date: Sun, 25 Jan 2004 20:21:51 +0000	[thread overview]
Message-ID: <4014255F.9070006@blueyonder.co.uk> (raw)


> Adrian Bunk wrote:
> On Sun, Jan 25, 2004 at 03:14:51PM +0000, Sid Boyce wrote:
>  >> Linus Torvalds wrote:
>  > > > Problems with the exception table sorting?
>  > > >
>  > > > Does plain 2.6.2-rc1 work?
>  >> 2.6.2-rc1 works fine.
> 
>  > Could you back out ("patch -p1 -R < ..." or manually remove the lines)
>  > the patch below and retry 2.6.2-rc1-mm2?
> 
> 
> 
>  > TIA
>  > Adrian
> 
> 
>  > --- 25/Makefile~use-funit-at-a-time 2004-01-14 00:56:05.000000000 -0800
>  > +++ 25-akpm/Makefile 2004-01-14 00:56:05.000000000 -0800
>  > @@ -445,6 +445,10 @@ ifdef CONFIG_DEBUG_INFO
>  > CFLAGS += -g
>  > endif
> 
>  > +# Enable unit-at-a-time mode when possible. It shrinks the
>  > +# kernel considerably.
>  > +CFLAGS += $(call check_gcc,-funit-at-a-time,)
>  > +
>  > # warn about C99 declaration after statement
>  > CFLAGS += $(call check_gcc,-Wdeclaration-after-statement,)

I commented out the line below. 2.6.2-rc1-mm3 is now up and running, 
thanks.

CFLAGS += $(call check_gcc,-funit-at-a-time,)

Regards
Sid.




-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.

             reply	other threads:[~2004-01-25 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 20:21 Sid Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-25 15:14 2.6.2-rc1-mm2 kernel oops Sid Boyce
2004-01-25 18:08 ` Adrian Bunk
2004-01-25 14:20 Sid Boyce
2004-01-25 20:11 ` John Stoffel
2004-01-25 20:34   ` Sid Boyce
2004-01-25 23:14     ` Eric
2004-01-25 23:25       ` Andrew Morton
2004-01-26  0:04         ` Andrew Morton
2004-01-26  6:33           ` Eric
2004-01-23 23:15 Sid Boyce
2004-01-24  5:12 ` Andrew Morton
2004-01-24  6:26   ` Linus Torvalds

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=4014255F.9070006@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.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.