From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: kernel make install - why don't we make it easy like on ia32?
Date: Mon, 25 Mar 2002 22:58:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905335@msgid-missing> (raw)
>>>>> On Tue, 19 Mar 2002 22:38:02 -0800, Piet/Pete Delaney <piet@sgi.com> said:
Piet> I was wondering why the ia32 style of installing boot stuff
Piet> like /boot/vmlinuz that done in:
Piet> arch/i386/boot/Makefile and arch/i386/boot/install.sh
Piet> isn't being done for ia64.
Piet> I'm thinking of makeing a few tweaks to the ia32 version to
Piet> copy kernel stuff to /boot and /boot/efi. I've been using a
Piet> hack on the top level kernel Makefile but it's a hack to do it
Piet> there. The ia32 paradigm seems fine; so why isn't it done for
Piet> ia64. Even after applying the ia64 patch to linux-2.4.18, a
Piet> 'make install' in the top level kernel Makefile still breaks.
No particular reasons. Just a case of something I'd never want to use
myself and nobody else sending a patch.
--david
reply other threads:[~2002-03-25 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590701905335@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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