public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:3.0 commit in: targets/support/
Date: Wed, 19 Feb 2014 17:47:48 +0000 (UTC)	[thread overview]
Message-ID: <1392831756.55d7d3dad42c3206e1eb67122a0bc3d35de1b40c.dol-sen@gentoo> (raw)

commit:     55d7d3dad42c3206e1eb67122a0bc3d35de1b40c
Author:     Guy Martin <gmsoft <AT> gentoo <DOT> org>
AuthorDate: Wed Feb  5 10:40:05 2014 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Wed Feb 19 17:42:36 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=55d7d3da

Use the system's iplboot to be sure it matches palo's version.

For hppa, cdtar is a bad idea because the iplboot version in the tar file
might not match palo's version.

---
 targets/support/bootloader-setup.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/targets/support/bootloader-setup.sh b/targets/support/bootloader-setup.sh
index b76b5c4..d9e2620 100755
--- a/targets/support/bootloader-setup.sh
+++ b/targets/support/bootloader-setup.sh
@@ -41,6 +41,8 @@ case ${clst_hostarch} in
 	;;
 	hppa)
 		# NO SOFTLEVEL SUPPORT YET
+		mkdir -p $1/boot
+
 		icfg=$1/boot/palo.conf
 		kmsg=$1/boot/kernels.msg
 		hmsg=$1/boot/help.msg
@@ -54,6 +56,9 @@ case ${clst_hostarch} in
 			my_kopts="${my_kopts} ${kopts}"
 		done
 
+		# copy the bootloader for the final image
+		cp /usr/share/palo/iplboot $1/boot/
+
 		echo "--commandline=0/${boot_kernel_common_name} initrd=${first}.igz ${default_append_line} ${my_kopts}" >> ${icfg}
 		echo "--bootloader=boot/iplboot" >> ${icfg}
 		echo "--ramdisk=boot/${first}.igz" >> ${icfg}


             reply	other threads:[~2014-02-19 17:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 17:47 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-28 11:41 [gentoo-commits] proj/catalyst:3.0 commit in: targets/support/ Raúl Porcel
2014-10-26 12:27 Raúl Porcel
2014-04-20 13:41 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-03-03 16:07 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2013-11-21  9:06 Brian Dolbec
2013-11-21  9:06 Brian Dolbec
2013-11-21  9:06 Brian Dolbec
2013-11-21  9:06 Brian Dolbec

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=1392831756.55d7d3dad42c3206e1eb67122a0bc3d35de1b40c.dol-sen@gentoo \
    --to=brian.dolbec@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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