buildroot/package/flex/flex.mk, branch 2017.08.1

flex: use the new gettext logic

2017-07-04T23:27:25+00:00

This commit switches to use the new gettext logic, which involves: - using TARGET_NLS_DEPENDENCIES instead of hand-encoded dependencies on gettext/host-gettext - dropping BR2_PACKAGE_GETTEXT selection Signed-off-by: Thomas Petazzoni

flex: remove bogus comment

2017-07-04T17:09:42+00:00

The comment that explains why we were defining HOST_FLEX_DEPENDENCIES instead of inheriting from FLEX_DEPENDENCIES no longer makes sense, since we remove such automatic inheritance of host dependencies from target dependencies a while ago. Signed-off-by: Thomas Petazzoni Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

flex: only prevent the flex binary to be built for target, not for host

2017-05-23T13:48:02+00:00

We do want to build the flex binary when building host-flex since it's needed as a build dependency for other packages. Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

flex: bump version to 2.6.4

2017-05-11T19:43:53+00:00

- 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@. - 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 Signed-off-by: Thomas Petazzoni

flex: remove deprecated binary in target

2015-01-25T23:21:35+00:00

It's been deprecated for a year now so remove the option. Also rename patch to new naming convention. Signed-off-by: Gustavo Zacarias Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

flex: delete broken flex++ symlink from target

2014-07-29T21:54:22+00:00

When flex is built for the target without installing the flex binary, a flex++ symlink installed by flex's Makefile points to the missing flex executable. This mod adds a post target install hook to remove the broken symlink. Signed-off-by: Danomi Manchego Signed-off-by: Thomas Petazzoni

Revert "flex: Version bump 2.5.39"

2014-04-05T13:21:36+00:00

The flex bump breaks at least two packages: - host-thrift, see http://autobuild.buildroot.org/results/759/7590122fd85b644ae0886a127005188d1f882bef/ - ipsec-tools, see http://autobuild.buildroot.org/results/238/238296556663d52015beb43df97106f6e164ce55/ No simple fix was found for now, so reverting is the easiest solution until some time is found to look at doing a flex bump that doesn't break those packages. This reverts commit 931d9fbae78a6bb8006a2634e9322ac253cc86f4. Signed-off-by: Thomas Petazzoni

flex: Version bump 2.5.39

2014-04-03T19:24:44+00:00

Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

Normalize separator size to 80

2013-06-06T20:30:24+00:00

Signed-off-by: Alexandre Belloni Signed-off-by: Peter Korsgaard

flex: fix autobuilder failures

2013-05-28T11:17:17+00:00

Since fe6a9e5e9d (flex: needs M4 at runtime), the autobuilders have been producing a number of flex related build failures. They have been hard to track down, because even on the same machine, with the same Git commit ID and the same configuration, the failure could not be reproduced. However, a close inspection of flex's config.log file allowed to find out what the problem was. In its configure script, flex uses the host-flex to generate a minimal example, and find out the name of the output file of flex. When the M4 environment is passed when building the target flex, it also affects the *execution* of the host-flex, which tries to use /usr/bin/m4 (which doesn't exist in the autobuilder machines) instead of the one built in $(HOST_DIR)/usr/bin/m4. So generating the minimal example fails. And this is where what I could reproduce and what the autobuilders script produce differ: in my case, even though host-flex fails to run, it creates an empty lex.yy.c, which is enough to make the configure script happy. In the context of the autobuild scripts, this file is apparently not created at all, for an unknown reason, and this leads to the configure script to abort. The fix is to set ac_cv_path_M4. This will affect the default m4 used by the target flex, but it will not affect the m4 used by the host-flex. It allows the test made during the configure script to work properly, and therefore should fix the issue seen in the autobuilders. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard