From: Paul Bame <bame@fc.hp.com>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] PALO/kernel-build change proposal
Date: Wed, 13 Jun 2001 11:31:38 -0600 [thread overview]
Message-ID: <E15AEUU-0004qi-00@noam.fc.hp.com> (raw)
Many of us are accustomed to the way 'make palo' works in our kernel
source tree (it goes over to the palo source tree, builds palo, and
then utilizes the palo Makefile to produce a bootable image). I want
to convert to a model based on palo being a separate stable piece
of software for which you may not even have sources. Many of us are
probably also not using 'palo.conf' files, which are the norm for self-
hosted operation.
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.
I propose that 'make palo' be changed to simply run 'palo -f ./palo.conf'
after vmlinux is built. This means palo would have to be in the $PATH
and that the top-level linux source directory would contain a
suitable palo.conf file. I've been using this model for cross-compiling
for several months and like it. I would document how xc-ers can best
compile and "install" palo as well as supply a palo.conf file with
our typical configurations.
What is 'make palo' today would be changed to 'make buildrunpalo'. The
longer name is more truthful and less convenient on purpose.
Feedback?
-P
next reply other threads:[~2001-06-13 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 17:31 Paul Bame [this message]
2001-06-13 21:22 ` [parisc-linux] PALO/kernel-build change proposal Grant Grundler
2001-06-15 16:52 ` Paul Bame
2001-06-17 15:03 ` Andrew Shugg
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=E15AEUU-0004qi-00@noam.fc.hp.com \
--to=bame@fc.hp.com \
--cc=parisc-linux@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