buildroot/package/flex, branch 2016.02

package: kill pointless text justification

2015-04-23T07:47:08+00:00

Signed-off-by: Gustavo Zacarias Acked-by: Arnout Vandecappelle (Essensium/Mind) 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

package: add hashes for SourceForge-hosted packages

2014-12-28T21:21:16+00:00

Since SourceForge sometimes serves us faulty tarballs, we can tons of autobuild failures: http://autobuild.buildroot.org/results/9fb/9fba5bf086a4e7a29e5f7156ec43847db7aacfc4/ http://autobuild.buildroot.org/results/6c8/6c837b244c45ac3b3a887734a371cd6d226cf216/ ... Fix that by adding hash files for all SourceForge-hosted packages (thos etht did not already have it). We normally prefer to use hashes published by upstream, but hunting them all one by one is a tedious task, so those hashes were all locally computed with a script that searched for SF-hosted packages, downloades the associated tarball, computed the hash, and stored it in the corresponding .hash file. Also, SF publishes sha1 hashes, while I used the stronger sha256, since sha1 is now considered to be relatively weak. Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Thomas Petazzoni Cc: Maxime Hadjinlian Cc: Richard Braun Cc: Nathaniel Roach Signed-off-by: Thomas Petazzoni

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

flex: change config text of 'target binary' option

2014-01-21T20:57:43+00:00

The buildroot manual contains a list of deprecated items, with their config title text, and the location in the config menu. If the config text does not mention a package name, this can be confusing. For example, the symbol BR2_PACKAGE_FLEX_BINARY has as text: 'Install tool in the target', which outside of the flex context makes no sense at all. To make sure the deprecated packages list in the manual is understandable, rename the (deprecated) flex 'target binary' config option. Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard

deprecated handling: introduce BR2_DEPRECATED_SINCE_xxxx_xx

2014-01-10T14:03:53+00:00

In order to keep better track of when a feature got deprecated, and hence when it can be removed, a new set of symbols BR2_DEPRECATED_SINCE_xxxx_xx is introduced. These symbols are automatically selected when BR2_DEPRECATED is selected, and thus are transparent to the user. A deprecated feature will no longer depend on BR2_DEPRECATED directly, but rather on the appropriate BR2_DEPRECATED_SINCE_xxxx_xx. If that symbol does not yet exist, it has to be created in Config.in. When removing a deprecated feature, one should also check whether this was the last feature using the BR2_DEPRECATED_SINCE_xxxx_xx symbol, in which case the latter can be removed from Config.in. A followup patch will make sure the overview is added to the list of deprecated features in the manual, so that a buildroot core developer can easily determine which features to remove in a given development cycle. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

package: deprecate some more development tools

2013-12-27T18:54:05+00:00

Since some time, we have removed the support to build a toolchain for the target, and therefore the support for several development tools on the target. This commit deprecates a few additional development tools: m4, bison, flex and gob2. For flex, we retain the ability to build libfl, we only deprecated the ability to build the flex binary itself. The original motivation for this patch is that m4 is causing build issues in some configurations, but there isn't really much incentive to fix this package for the target, since it is not really useful for embedded Linux systems. Bison, Flex and Gob2 are deprecated because they are reverse dependencies of m4. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN"

Config.in files: add missing dependencies to toolchain option comments

2013-11-10T22:59:57+00:00

When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) (untested) Signed-off-by: Peter Korsgaard