From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "syslinux: drop patch 0003, not needed after gnu-efi update"
Date: Mon, 14 Aug 2017 22:09:53 +0200 [thread overview]
Message-ID: <20170814220953.45dcf706@windsurf> (raw)
In-Reply-To: <20170813232835.18414-1-arnout@mind.be>
Hello,
On Mon, 14 Aug 2017 01:28:35 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> It turns out that this patch is still needed, since with some versions
> of binutils the error still occurs.
>
> Partially fixes: https://gitlab.com/arnout/buildroot/-/jobs/28979377
>
> This reverts commit 644c024edeb7e20bd96ce4426aeca2cbcd74d9b9.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Beno?t Allard <benoit.allard@greenbone.net>
> ---
> The failing ts5x00_defconfig also requires a kernel bump
The problem with this is that you are going to run into the problem I
reported at:
http://lists.busybox.net/pipermail/buildroot/2017-July/195927.html, i.e
the --no-dynamic-linker option doesn't exist in old binutils versions,
and will therefore cause a build failure.
BTW Arnout, you should not expect any feedback from Beno?t, he has left
his previous employer, and explicitly removed himself from the syslinux
developer:
https://git.buildroot.org/buildroot/commit/DEVELOPERS?id=74a1e8f9f220c8fb95abe1de67ee5441b7c449e7.
He will most likely not even receive your e-mail.
Therefore, we are on our own to figure out this one :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-14 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 23:28 [Buildroot] [PATCH] Revert "syslinux: drop patch 0003, not needed after gnu-efi update" Arnout Vandecappelle
2017-08-14 20:09 ` Thomas Petazzoni [this message]
2017-08-15 14:53 ` Arnout Vandecappelle
2017-08-15 21:25 ` Arnout Vandecappelle
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=20170814220953.45dcf706@windsurf \
--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