mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kbuild devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL (updated)] kbuild updates
Date: Tue, 16 Oct 2007 14:23:36 -0700	[thread overview]
Message-ID: <20071016142336.f9129f40.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20071016211101.GA4093@gentoox2.trippelsdorf.de>

On Tue, 16 Oct 2007 23:11:01 +0200 Markus Trippelsdorf wrote:

> On Mon, Oct 15, 2007 at 10:50:18PM +0200, Sam Ravnborg wrote:
> > 
> > The kbuild patches has been rebased on top of -linus after
> > the x86 merge.
> > The patch that caused ARCH to be unset has been withdrawn for
> > now. It had additional issues and I need to do additional changes
> > to get it included - in other words it will await next merge window.
> > 
> > The following patches does almost clear my patch queue. I have some
> > fixes pending but need some more time to check them out.
> > On top of this I have a few reports from -mm that needs attention too.
> > So in other words I expect a smaller set of patches for -rc1 or -rc2
> > as my time permits.
> > 
> > In addition to latest pull request this one includes:
> > - rename of
> > 	CFLAGS => KBUILD_CFLAGS
> > 	AFLAGS => KBUILD_AFLAGS
> > 	CPPFLAGS => KBUILD_CPPFLAGS
> >     rationale behind this was two-fold:
> >     1) Do not let the CFLAGS environment variable impact all builds
> >     2) Allow one to specify addition gcc options on the commandline
> >        as make CLFAGS=-Os ...
> > - introducing ccflags-y, asflags-y and ldflags-y as the future
> >   replacement of the EXTRA_* variants.
> > 
> > 
> > The majority (line wise) is update of generated files.
> > The rest is almost all one-liners so nothing controversial.
> > The file with most lines changed is makefiles.txt!
> > 
> 
> Bisecting shows that:
> 
> commit f77bf01425b11947eeb3b5b54685212c302741b8
> 	Author: Sam Ravnborg <sam@neptun.(none)>
>  	Date:   Mon Oct 15 22:25:06 2007 +0200
> 
>     kbuild: introduce ccflags-y, asflags-y and ldflags-y
> 
> breaks booting with grub here. Grub stops with error 28: 
> Selected item cannot fit into memory.
> 
> Reverting the commit fixes the problem.

Wow.  I had a similar issue with lilo, but I had no idea
what may have caused it.  Thanks.


Fatal: Kernel /boot/kernel-2.6.23-git10 is too big
ERROR:  Failed to run lilo.


---
~Randy

  reply	other threads:[~2007-10-16 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 20:50 Sam Ravnborg
2007-10-16 21:11 ` Markus Trippelsdorf
2007-10-16 21:23   ` Randy Dunlap [this message]
2007-10-16 21:34   ` Ismail Dönmez
2007-10-16 22:04   ` Sam Ravnborg
2007-10-16 23:24 ` [PATCH] x86 boot: Build a bzImage again Eric W. Biederman

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=20071016142336.f9129f40.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®