From: Russell King <rmk@arm.linux.org.uk>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.0.0 release announcement
Date: Tue, 10 Apr 2001 13:14:12 +0100 [thread overview]
Message-ID: <20010410131412.A18973@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200104101047.f3AAl0h07395@snark.thyrsus.com>
In-Reply-To: <200104101047.f3AAl0h07395@snark.thyrsus.com>; from esr@snark.thyrsus.com on Tue, Apr 10, 2001 at 06:47:00AM -0400
On Tue, Apr 10, 2001 at 06:47:00AM -0400, Eric S. Raymond wrote:
> On 30 March 2001 at the Kernel Summit, Keith Owens and I worked out a
> transition schedule with Linus. Keith's rewrite of the makefile system and
> my configurator tools are officially slated to replace the present system in
> the 2.5.1 to 2.5.2 timeframe. That, of course, is contingent on us not
> screwing up :-).
Assuming that Keiths makefiles can do everything that architecture
maintainers need it to do.
Currently, one of the many things I'm doing is trying to sort out a
working kbuild-2.5 for the ARM tree. I have some stuff done, but there
are several things that I'm definitely not happy with, and there is
currently a whole scoop of stuff which I haven't yet found a way for
kbuild-2.5 to handle. Its looking like the ARM trees use of kbuild-2.5
will be even more messy than its use of the current build system.
(We have around 60 machines, which key both which files get built, the
text and data address of the running kernel image, the text and data
address of the decompressor, and which vmlinux.lds.in file we use to
link the kernel. This is currently my biggest problem that kbuild-2.5
doesn't seem to be able to handle at present. Note that it is not
acceptable that users should have to type in 5 or so apparantly
meaningless hex addresses when they configure the kernel.)
I've yet to hear back from Keith on the issues I have with kbuild-2.5,
but I'm hopeful that he has some good suggestions...
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-10 12:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 10:47 CML2 1.0.0 release announcement Eric S. Raymond
2001-04-10 12:14 ` Russell King [this message]
2001-04-11 19:43 ` davej
2001-04-11 20:04 ` Christoph Hellwig
2001-04-11 20:16 ` Dave Jones
2001-04-11 20:27 ` Christoph Hellwig
2001-04-11 22:23 ` Alan Cox
2001-04-11 23:19 ` esr
2001-04-11 23:30 ` Alan Cox
2001-04-11 23:33 ` Alan Cox
2001-04-12 0:45 ` esr
[not found] ` <3AD4FC54.C86AACBE@mandrakesoft.com>
2001-04-12 1:28 ` esr
2001-04-12 1:43 ` CML2 1.0.0 doesn't remember configuration changes jeff millar
2001-04-12 2:50 ` esr
2001-04-12 5:35 ` jeff millar
2001-04-12 2:06 ` esr
2001-04-12 21:20 ` Ingo Oeser
2001-04-14 2:11 ` Eric S. Raymond
2001-04-14 2:29 ` Jeff Garzik
2001-04-14 4:33 ` Nicolas Pitre
2001-04-12 10:45 ` CML2 1.0.0 release announcement Alan Cox
2001-04-11 22:20 ` esr
2001-04-12 7:09 ` Albert D. Cahalan
2001-04-12 8:57 ` Jamie Lokier
2001-04-12 10:57 ` esr
[not found] <fa.i13tmhv.9kga3t@ifi.uio.no>
[not found] ` <fa.g0offov.1jmmkh9@ifi.uio.no>
2001-04-12 8:50 ` Giacomo Catenazzi
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=20010410131412.A18973@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=esr@snark.thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox