From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13681] New: syslinux build install tools
Date: Tue, 30 Mar 2021 13:40:44 +0000 [thread overview]
Message-ID: <bug-13681-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13681
Bug ID: 13681
Summary: syslinux build install tools
Product: buildroot
Version: 2021.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: moelzerjens at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The way the syslinux install tools are currently built doesn't make a lot of
sense imho: The only tool that's installed is extlinux and that is only built
for the host. That's not really useful as extlinux needs root, so it can't
cleanly be used to automatically generate disk images on the host. The
syslinux/mtools-syslinux tools that could be used for disk image generation
without root on the host are only built for the target and not installed (they
can be found in the build folder).
Therefore I propose the following improvements:
1) Provide an option to build extlinux for the target like the grub2 package
"install tools" option (BR2_TARGET_GRUB2_INSTALL_TOOLS).
2) Build the syslinux/mtools-syslinux installer for the host to facilitate
scripted disk image generation. It might be beneficial to integrate the
syslinux patches from Yocto Project [1] that extend syslinux support to
ext2/3/4 as well.
[1]
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-devtools/syslinux/syslinux/
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-30 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 13:40 bugzilla at busybox.net [this message]
2021-03-30 19:44 ` [Buildroot] [Bug 13681] syslinux build install tools bugzilla at busybox.net
2024-06-15 14:58 ` bugzilla
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=bug-13681-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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