From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Roman Zippel <zippel@linux-m68k.org>,
"Christian T. Steigies" <cts@debian.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: kernel-image-2.6.7
Date: Sun, 29 Aug 2004 14:11:53 +0200 [thread overview]
Message-ID: <20040829121153.GA30301@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0408291324020.10903@teasel.sonytel.be>
On Sun, Aug 29, 2004 at 01:38:02PM +0200, Geert Uytterhoeven wrote:
> Conclusions: gcc 2.95.2 and binutils 2.9.5 are fine for compiling 2.6.x kernels
> for m68k, but:
> - You need a newer binutils for building initramfs (make usr/)
> - You need a newer binutils for building modular kernels with
> CONFIG_MODVERSIONS=y
Is this something you can make a check for in arch/m68k/Makefile?
Just so others don't hit the same trap..
Sam
next prev parent reply other threads:[~2004-08-29 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040809073126.GA4669@skeeve>
[not found] ` <Pine.LNX.4.58.0408221129590.25793@anakin>
[not found] ` <Pine.LNX.4.58.0408221145090.25793@anakin>
[not found] ` <20040822101914.GA7480@skeeve>
[not found] ` <Pine.GSO.4.58.0408221224310.12638@waterleaf.sonytel.be>
[not found] ` <Pine.LNX.4.58.0408221333460.13834@anakin>
[not found] ` <4128C3F4.6070507@linux-m68k.org>
[not found] ` <Pine.GSO.4.58.0408230947190.29370@waterleaf.sonytel.be>
2004-08-25 20:50 ` kernel-image-2.6.7 Geert Uytterhoeven
2004-08-25 22:17 ` kernel-image-2.6.7 Andreas Schwab
2004-08-26 19:56 ` kernel-image-2.6.7 Sam Ravnborg
2004-08-29 11:38 ` kernel-image-2.6.7 Geert Uytterhoeven
2004-08-29 12:11 ` Sam Ravnborg [this message]
2004-08-30 8:53 ` kernel-image-2.6.7 Geert Uytterhoeven
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=20040829121153.GA30301@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=cts@debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=zippel@linux-m68k.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®