From: Kevin Zhao <kevin.zhaoshuai@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Cc: kevin.zhaoshuai@gmail.com
Subject: [gentoo-catalyst][PATCH 2/3] Modify the mkisofs parameter of ppc64 little-endian.
Date: Mon, 11 Jan 2016 23:55:14 -0500 [thread overview]
Message-ID: <1452574514-16857-1-git-send-email-kevin.zhaoshuai@gmail.com> (raw)
ppc64 little-endian has different archtecture and new
boot parameters.Don't need the hfs and mapping files
as it in Big-endian.Also tweak the code of Big-endian.
Signed-off-by: Kevin Zhao <kevin.zhaoshuai@gmail.com>
---
targets/support/create-iso.sh | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/targets/support/create-iso.sh b/targets/support/create-iso.sh
index b4077c3..e333921 100755
--- a/targets/support/create-iso.sh
+++ b/targets/support/create-iso.sh
@@ -211,8 +211,22 @@ case ${clst_hostarch} in
"${clst_target_path}/ppc/bootinfo.txt"
fi
+ flags=( -r -U -chrproot )
echo ">> Running mkisofs to create iso image...."
- run_mkisofs -r -U -chrp-boot -netatalk -hfs -probe -map "${clst_target_path}"/boot/map.hfs -part -no-desktop -hfs-volid "${clst_iso_volume_id}" -hfs-bless "${clst_target_path}"/boot -hide-hfs "zisofs" -hide-hfs "stages" -hide-hfs "distfiles" -hide-hfs "snapshots" -J ${mkisofs_zisofs_opts} -V "${clst_iso_volume_id}" -o "${1}" "${clst_target_path}"/
+ if [[ ${clst_subarch} == *le ]]
+ then
+ flags+=(
+ -v -T -l -cache-inodes
+ )
+ else
+ flags+=(
+ -netatalk -hfs -probe -map "${clst_target_path}"/boot/map.hfs
+ -part -no-desktop -hfs-volid "${clst_iso_volume_id}" -hfs-bless "${clst_target_path}"/boot -hide-hfs
+ "zisofs" -hide-hfs "stages" -hide-hfs "distfiles" -hide-hfs "snapshots" -J ${mkisofs_zisofs_opts}
+ )
+ fi
+ run_mkisofs "${flags[@]}" \
+ -V "${clst_iso_volume_id}" -o "${1}" "${clst_target_path}"
;;
sparc*)
# Old silo (<=1.2.6) requires a specially built mkisofs
--
2.1.0
reply other threads:[~2016-01-12 4:56 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=1452574514-16857-1-git-send-email-kevin.zhaoshuai@gmail.com \
--to=kevin.zhaoshuai@gmail.com \
--cc=gentoo-catalyst@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