From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] syslinux on target
Date: Wed, 8 Oct 2014 19:09:23 +0200 [thread overview]
Message-ID: <20141008170923.GA4718@free.fr> (raw)
In-Reply-To: <543520E6.3000307@gmail.com>
Zoltan, All,
On 2014-10-08 13:32 +0200, Zoltan Gyarmati spake thusly:
> is there any supported way to install syslinux (the utility which installs
> syslinux on a partition) on the target? If not (i couldn't find it), is
> there any specific reason to not support this in Buildroot?
Currently, we do not install 'syslinux' (the command) on the target.
Neither do we install 'extlinux' or 'isolinux' (the commands).
syslinux (the package) is very special. It does not cross-compile nicely
in my experience. So, we build it as a native package, using the native
host toolchain.
Also, we fully install syslinux in the host/ directory, even though it
contains blobs (e.g. the .c32 modules) for the target. That's the
traditional way syslinux exxpects to fins it files.
Finally, even if we were to install the 'syslinux' (or 'extlinux' or
'isolinux') programs in the target, we'd also need to install a few
other files, such as:
- the mbr blobs: for BIOS- or GPT- or CD-based boots, 'alt' versions,
the '_c' and '_f' versions (wtf are those?),
- all of the .c32 modules (even though only a sbuset is really used to
actually boot the target,
- and a lot of other stuff.
Also, the reason is that Buildroot mostly targets simple devices, and we
did not so far see a valid reason for having the syslinux tools on the
target.
So, what is the use-case to have those tools on the target?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-10-08 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 11:32 [Buildroot] syslinux on target Zoltan Gyarmati
2014-10-08 17:09 ` Yann E. MORIN [this message]
2014-10-08 19:44 ` Zoltan Gyarmati
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=20141008170923.GA4718@free.fr \
--to=yann.morin.1998@free.fr \
--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