From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 next] flex: bump version to 2.6.4
Date: Mon, 22 May 2017 21:58:12 +0200 [thread overview]
Message-ID: <20170522215812.078b9c7b@free-electrons.com> (raw)
In-Reply-To: <20170510135139.30976-1-Vincent.Riera@imgtec.com>
Hello,
On Wed, 10 May 2017 14:51:39 +0100, Vicente Olivert Riera wrote:
> - 0001 patch removed. It doesn't apply on this version and is also not
> necessary since the AR binary is now handled correctly with AR = @AR at .
> - 0002 patch removed. It's already included in this release:
> https://github.com/westes/flex/commit/a5cbe929ac3255d371e698f62dc256afe7006466
> - The flex project has moved to GitHub, so modify the URLs in both
> flex.mk and Config.in files.
> - The sed command over Makefile.in to prevent the flex binary to be
> built fails, so remove it. That logic has been moved to
> src/Makefile.in, and whenever we disable the flex binary to be built
> then the compilation fails when building the documentation because
> some bits require "../src/flex", which is the flex binary.
> We prevent building the flex binary and the documentation using a new
> patch.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
This commit causes a major bug: host-flex no longer builds/installs the
"flex" program. This will cause a huge number of build failures,
because there are a lot of packages that depend on host-flex to get the
flex program.
Could you send a patch that fixes this? Either revert back to the
previous solution of patching the Makefile.in in flex.mk, or adding a
proper configure.ac option to enable/disable building/installation the
flex program.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-22 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 13:51 [Buildroot] [PATCH v3 next] flex: bump version to 2.6.4 Vicente Olivert Riera
2017-05-11 19:47 ` Thomas Petazzoni
2017-05-22 19:58 ` 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=20170522215812.078b9c7b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox