Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] syslinux: Use the host compiler to build extlinux
Date: Mon, 2 Oct 2017 21:15:47 +0200	[thread overview]
Message-ID: <20171002211547.4942e28d@windsurf.home> (raw)
In-Reply-To: <20170930233520.20143-1-casantos@datacom.ind.br>

Hello,

On Sat, 30 Sep 2017 20:35:20 -0300, Carlos Santos wrote:
> Like the utilities, it is meant to run on the host machine, hence must
> be built using the host toolchain.
> 
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>

It is not entirely clear if everybody agrees that "extlinux" is a host
or a target program.

Beno?t Allard, who used to work on the syslinux package in Buildroot
wrote in http://www.syslinux.org/archives/2017-April/025755.html:

"""
1. utilities required during the build (prepcore)
2. utilities meant to be run in the target operating-system (isohybrid,
  memdisk, the extlinux installer, ...)
3. utilities used to boot the operating system
"""

So he was considering the extlinux installer as a program for the
target.

A few years earlier, another person on the Buildroot mailing list, also
wanted to have the extlinux installer on the target:
http://buildroot-busybox.2317881.n4.nabble.com/syslinux-on-target-td81294.html.

So, I'm not sure. Perhaps we need a host-syslinux package to install
those utilities ?

Or perhaps I'm being too complicated here, we should just merge your
patch, and adjusts when/if someone complains ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-10-02 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30 23:13 [Buildroot] [PATCH] syslinux: Use the host compiler to build extlinux Carlos Santos
2017-09-30 23:35 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-10-02 19:15   ` Thomas Petazzoni [this message]
2017-10-02 20:36     ` Carlos Santos
2017-10-13 15:10       ` Carlos Santos
2018-04-01 15:48   ` Thomas Petazzoni

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=20171002211547.4942e28d@windsurf.home \
    --to=thomas.petazzoni@free-electrons.com \
    --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