All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] syslinux: build with the target toolchain
Date: Thu, 6 Apr 2017 17:13:23 +0200	[thread overview]
Message-ID: <20170406171323.13d11cc6@free-electrons.com> (raw)
In-Reply-To: <1491473086-16647-1-git-send-email-benoit.allard@greenbone.net>

Hello,

On Thu,  6 Apr 2017 12:04:46 +0200, Beno?t Allard wrote:
> Until now, the host toolchain was used to build syslinux, as it was
> not possible to build a 32-bit syslinux with a x86-64 toolchain.
> 
> However, syslinux requires gnu-efi, and gnu-efi is built using the
> target toolchain. Mixing different toolchains doesn't work well, so
> this commit changes the syslinux package to use the target toolchain
> for syslinux as well. This is made possible by patches
> 0003-Fix-ldlinux.elf-Not-enough-room-for-program-headers-.patch and
> 0004-memdisk-Force-ld-output-format-to-32-bits.patch.
> 
> Since syslinux also contains some utilities that have to run on the
> host, those have to continue being built with the host toolchain,
> which requires patch 0005-utils-Use-the-host-toolchain-to-build.patch.
> 
> This was tested using a Buildroot's built x86_64 toolchain, and
> checked that the output binaries are 32-bits. It was tested as well if
> they actually boot on hardware.
> 
> Signed-off-by: Beno?t Allard <benoit.allard@greenbone.net>

Thanks, this now builds fine. However, in output/host/usr/bin, I still
have a program built with the target toolchain:

$ file output/host/usr/bin/syslinux
output/host/usr/bin/syslinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, not stripped

See the /lib/ld-musl-x86_64 interpreter? This means it has been built
against the musl C library, and therefore with the target toolchain.

What is this program useful for?

Best regards,

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

  reply	other threads:[~2017-04-06 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 10:09 [Buildroot] [PATCH] syslinux: Builds with the target toolchain Benoît Allard
2017-04-05 11:02 ` Thomas Petazzoni
2017-04-05 13:38   ` Benoît Allard
2017-04-05 14:48     ` Arnout Vandecappelle
2017-04-05 13:28 ` [Buildroot] [PATCH v2 1/2] " Benoît Allard
2017-04-05 13:28   ` [Buildroot] [PATCH v2 2/2] Take ownership of the (orphaned) syslinux package Benoît Allard
2017-04-05 14:51     ` Arnout Vandecappelle
2017-04-05 19:07     ` Thomas Petazzoni
2017-04-05 20:25   ` [Buildroot] [PATCH v2 1/2] syslinux: Builds with the target toolchain Thomas Petazzoni
2017-04-06 10:04   ` [Buildroot] [PATCH v4 1/1] syslinux: build " Benoît Allard
2017-04-06 15:13     ` Thomas Petazzoni [this message]
2017-04-07  8:06       ` Benoît Allard
2017-04-07  8:16         ` Thomas Petazzoni
2017-04-07  9:05     ` [Buildroot] [PATCH v5] " Benoît Allard
2017-04-08 14:08       ` Thomas Petazzoni
2017-04-11  7:45         ` Benoît Allard
2017-04-12  8:34           ` Thomas Petazzoni
2017-04-24 19:19       ` Peter Korsgaard

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=20170406171323.13d11cc6@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.