From: Juan Quintela <quintela@mandrakesoft.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: mfedyk@matchmail.com (Mike Fedyk),
Wayne.Brown@altec.com, linux-kernel@vger.kernel.org,
kaos@ocs.com.au (Keith Owens)
Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3
Date: 20 May 2002 16:29:36 +0200 [thread overview]
Message-ID: <m2y9eex57z.fsf@demo.mitica> (raw)
In-Reply-To: <200205200509.g4K59a9494917@saturn.cs.uml.edu>
>>>>> "albert" == Albert D Cahalan <acahalan@cs.uml.edu> writes:
albert> Mike Fedyk writes:
>> On Sat, May 18, 2002 at 12:32:25PM -0500, Wayne.Brown@altec.com wrote:
>>> I never expected everyone to abandon their own needs to satisfy mine.
>>> It would be nice if they tried to accomodate my needs while satisfying
>>> their own, but I didn't expect that either.
>>
>> IIRC, Kbuild-2.5 already silently accepts all of the old kbuild-2.4
>> commands without problems.
>>
>> As long as you end up running "make install" the rest of the old commands
>> will be ignored. You can go on with all of the old commands, if you want
>> without any trouble.
albert> Well, not everybody trusts "make install" to do something useful.
albert> I'd do something like this:
albert> make clean
albert> bzip2 -dc ../foo.bz2 | patch -E -s -p1
albert> make menuconfig
albert> time script build-log
albert> make vmlinux && make modules && make modules_install && exit
this is standard
albert> cp vmlinux /boot/vmlinux-2.5.16
albert> cp System.map /boot/System.map-2.5.16
albert> cp .config /boot/config-2.5.16
albert> sync
albert> su -
albert> joe /etc/yaboot.conf
albert> sync
albert> exit
You can put that thing in /sbin/install and actual build system will
do what you want. Here we modify grub || lilo in x86 in that script,
it is not difficult to automatize.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2002-05-20 14:24 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-18 10:25 kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3 Mike Galbraith
2002-05-18 17:32 ` Wayne.Brown
2002-05-18 18:11 ` Tomas Szepe
2002-05-18 21:15 ` DervishD
2002-05-20 4:31 ` Mike Fedyk
2002-05-20 5:09 ` Albert D. Cahalan
2002-05-20 5:18 ` Keith Owens
2002-05-20 14:29 ` Juan Quintela [this message]
2002-05-20 5:11 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-05-19 10:26 Mike Galbraith
2002-05-18 6:05 Wayne.Brown
2002-05-18 16:50 ` John Weber
2002-05-18 5:09 Wayne.Brown
2002-05-18 5:23 ` David Lang
2002-05-18 13:11 ` Diego Calleja
2002-05-17 22:59 Wayne.Brown
2002-05-17 23:14 ` Robert Love
2002-05-18 4:01 ` Horst von Brand
2002-05-18 12:57 ` Diego Calleja
2002-05-17 20:53 Wayne.Brown
2002-05-17 21:14 ` Andrew Morton
2002-05-17 21:42 ` William Lee Irwin III
2002-05-17 22:16 ` Kai Germaschewski
2002-05-17 22:34 ` William Lee Irwin III
2002-05-17 22:40 ` Larry McVoy
2002-05-18 0:41 ` Oliver Xymoron
2002-05-17 22:09 ` Nicolas Pitre
2002-05-18 0:38 ` Oliver Xymoron
2002-05-17 19:51 Wayne.Brown
2002-05-17 20:09 ` Dave Jones
2002-05-17 20:25 ` Diego Calleja
2002-05-18 13:15 ` Paul P Komkoff Jr
2002-05-17 14:56 James Bottomley
2002-05-17 14:21 Wayne.Brown
2002-05-17 17:37 ` Adam Kropelin
2002-05-17 18:00 ` Robert Love
2002-05-16 22:42 Keith Owens
2002-05-17 0:10 ` Nicolas Pitre
2002-05-17 3:30 ` Tomas Szepe
2002-05-17 7:55 ` Russell King
2002-05-17 8:42 ` Miles Lane
2002-05-17 13:11 ` Dave Jones
2002-05-17 13:09 ` Denis Vlasenko
2002-05-17 8:17 ` Tomas Szepe
2002-05-17 13:39 ` Denis Vlasenko
2002-05-17 1:50 ` jeff millar
2002-05-17 2:04 ` Keith Owens
2002-05-17 2:26 ` Dave Jones
2002-05-17 7:11 ` Kenneth Johansson
2002-05-17 15:13 ` Nicolas Pitre
2002-05-17 15:19 ` Tomas Szepe
2002-05-17 15:42 ` Nicolas Pitre
2002-05-18 1:39 ` Keith Owens
2002-05-18 2:11 ` Nicolas Pitre
2002-05-18 2:19 ` Keith Owens
2002-05-17 18:19 ` Diego Calleja
2002-05-19 15:46 ` Pavel Machek
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=m2y9eex57z.fsf@demo.mitica \
--to=quintela@mandrakesoft.com \
--cc=Wayne.Brown@altec.com \
--cc=acahalan@cs.uml.edu \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/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