From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/3] ed: add host package
Date: Sun, 16 Jul 2017 16:05:47 +0200 [thread overview]
Message-ID: <20170716160547.347fade2@windsurf> (raw)
In-Reply-To: <20170512142848.13956-1-Vincent.Riera@imgtec.com>
Hello,
On Fri, 12 May 2017 15:28:46 +0100, Vicente Olivert Riera wrote:
> This will be necessary for updating bc's version in a subsequent patch.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/ed/ed.mk | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
I had a look at all of this, and my feeling is the same as the
OpenEmbedded folks: this really sucks. Why on earth do they need "ed"?
Why don't they fix their build system to build fbc for the host?
See https://patchwork.openembedded.org/patch/140001/ for the feedback
from OpenEmbedded people. I really don't think there's a compelling
reason to upgrade to 1.07.1 for now, so let's keep 1.06 and avoid this
mess.
I've mailed the submitter of the OE patch, who said he would contact
the upstream GNU bc maintainer, in order to see if he got some
feedback. You are in Cc of this e-mail.
In addition, there was an issue in your patch: GNU bc has moved to GNU
GPLv3+ since this 1.07.1 release, so the licensing details should be
fixed as well.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-16 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 14:28 [Buildroot] [PATCH next 1/3] ed: add host package Vicente Olivert Riera
2017-05-12 14:28 ` [Buildroot] [PATCH next 2/3] bc: " Vicente Olivert Riera
2017-05-12 14:28 ` [Buildroot] [PATCH next 3/3] bc: bump version to 1.07.1 Vicente Olivert Riera
2017-07-03 16:47 ` Romain Naour
2017-07-16 14:05 ` Thomas Petazzoni [this message]
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=20170716160547.347fade2@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