Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PALO/kernel-build change proposal
Date: Sun, 17 Jun 2001 23:03:19 +0800	[thread overview]
Message-ID: <20010617230316.A3622@neep.com.au> (raw)
In-Reply-To: <200106132122.PAA01189@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Wed, Jun 13, 2001 at 03:22:10PM -0600

Grant Grundler said:
> Paul Bame wrote:
> > When self hosted, there's usually no need to run palo after every
> > kernel build since palo boots out of the file system by file name.
> > So I propose that the common self-hosted use model be to use simple
> > 'make' in the kernel tree [and make modules or whatever].  The
> > resulting 'vmlinux' file can then be copied to the desired location.
> 
> On x86, "make install" will do all the right things to install the
> freshly built kernel but doesn't do a damn thing for kernel modules.
> Need to run "make modules" and "make modules_install" to really make
> sure eveything is in sync.

As a Debian user I discovered the wonders of Manoj's kernel-package
suite to build Debian packages of kernel source/headers/image/docs from
a single kernel tree.  Certainly much easier to install the resulting
kernel-image-*.deb package than fuss about with the various Makefile
targets.  I suppose it would be unfriendly though to ask that this
become the standard means of building and installing hppa-linux kernels?

=)

I see nothing wrong with Paul's suggestion but hope that kernel-package
is educated about the changes for the hppa architecture.  I've grown
fond of it (or too lazy to go back?) ...

Andrew.

--
Andrew Shugg <andrew@neep.com.au>                   http://www.neep.com.au/

"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there?  Well I'd like to meet him.  I could do with a good laugh."

  parent reply	other threads:[~2001-06-17 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 17:31 [parisc-linux] PALO/kernel-build change proposal Paul Bame
2001-06-13 21:22 ` Grant Grundler
2001-06-15 16:52   ` Paul Bame
2001-06-17 15:03   ` Andrew Shugg [this message]
2001-06-17 16:14     ` Tom
2001-06-18  0:16       ` buggz
2001-06-18  1:05         ` Tom
2001-06-18  1:13           ` Matthew Wilcox
2001-06-17 20:15     ` Matthew Wilcox

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=20010617230316.A3622@neep.com.au \
    --to=andrew@neep.com.au \
    --cc=parisc-linux@lists.parisc-linux.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