From: Paul Bame <bame@fc.hp.com>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PALO/kernel-build change proposal
Date: Fri, 15 Jun 2001 10:52:55 -0600 [thread overview]
Message-ID: <E15Awq7-0000kt-00@noam.fc.hp.com> (raw)
In-Reply-To: Your message of "Wed, 13 Jun 2001 15:22:10 MDT." <200106132122.PAA01189@puffin.external.hp.com>
= > 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.
=
=
= How about "make lifimage"?
= That's the only reason I run "make palo" in the XC environment.
= Having a XC-palo in the environment is no problem.
= In the XC env, I don't expect "make install" to do the right thing (tm).
ok, I ammend my proposal so that what I just described as 'make palo' be
changed to 'make lifimage', and that what I just called 'make buildrunpalo',
which jumps into the source tree and builds palo among other things, retain
the name buildrunpalo. Howzzat?
next prev parent reply other threads:[~2001-06-15 16:57 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 [this message]
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=E15Awq7-0000kt-00@noam.fc.hp.com \
--to=bame@fc.hp.com \
--cc=grundler@puffin.external.hp.com \
--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