buildroot/package/beecrypt, branch 2017.08

package/beecrypt: remove c++ support

2017-06-24T14:50:16+00:00

Optional C++ support depends on icu, the icu version bump to 59.1 brought ABI-breaking changes http://site.icu-project.org/download/59#TOC-char16_t-in-C- which are incompatible with beecrypt. Since beecrypt did not get any updates upstream since 2009 and no package uses beecrypt's C++ support we disable this broken option. With C++ support removed patches 0002 & 0004 are not needed anymore. Fixes http://autobuild.buildroot.net/results/a1a/a1ad507371192ddecacab0df91f7b2a84c7c288d/ Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

package/beecrypt: needs host gcc >= 4.8 for icu support

2017-06-10T21:06:23+00:00

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

package/icu: bump version to 59.1

2017-06-05T13:51:04+00:00

According to the release notes "Compiler support for C++11 is now required for building the ICU libraries. GCC: version 4.8 and later has been tested." Added corresponding dependencies and reverse dependencies. Removed patch 0006 applied upstream. Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

boot, package: use SPDX short identifier for LGPLv2.1/LGPLv2.1+

2017-04-01T13:18:10+00:00

We want to use SPDX identifier for license string as much as possible. SPDX short identifier for LGPLv2.1/LGPLv2.1+ is LGPL-2.1/LGPL-2.1+. This change is done using following command. find . -name "*.mk" | xargs sed -ri '/LICENSE( )?[\+:]?=/s/LGPLv2.1(\+)?/LGPL-2.1\1/g' Signed-off-by: Rahul Bedarkar Signed-off-by: Thomas Petazzoni

beecrypt: arm assembly optimizations needs ARM instructions support

2016-06-27T14:33:07+00:00

Fixes: http://autobuild.buildroot.net/results/980/98034ebb086987fb8fc004672164f609f5a69543/ http://autobuild.buildroot.net/results/3bd/3bdba5cf7e901f8600e567b1b0eb0866d6dfc523/ So disable it for thumb(2)-only configurations (armv7m), similar to how we do it for m68k coldfire. Signed-off-by: Peter Korsgaard

beecrypt: fix compile for coldfire

2016-06-18T21:38:29+00:00

Package uses m68k optimization, which doesn't work with coldfire. These optimizations are disabled with --enable-debug. Fixes following autobuild failure: http://autobuild.buildroot.net/results/bbe57a096de207b78e069591e21ac5a79eab069e/ http://autobuild.buildroot.net/results/ab702e6db382b1975d0cd61feaba9812830e81e8/ Signed-off-by: Waldemar Brodkorb Signed-off-by: Peter Korsgaard

icu: remove BR2_ARCH_HAS_ATOMICS dependency

2016-01-26T20:26:08+00:00

The BR2_ARCH_HAS_ATOMICS was added because on ARC, atomic instructions may not be provided by the architecture and therefore the compiler does not provide the __sync_*() built-ins. However, since then, icu was changed and is now able to use C++11 atomics, or even no atomic operations at all. In fact, icu will: * If possible, it will use C++11 atomics, which internally rely on the __atomic built-ins. These are available since gcc 4.7, and all architectures provide it. On some architectures, you *must* link with libatomic, on some other architectures, they are available built-in, but in all cases, linking against libatomic does not harm. Thanks to this, even ARC with no atomic support (which was the original reason for adding the BR2_ARCH_HAS_ATOMICS) dependency builds fine, provided -latomic is added to LIBS. * If C++11 atomics are not available, then it falls back to __sync_*() built-ins, which allows compilers older than 4.7 to be supported. * If really no atomic mechanism is available, then it falls back to a basic implementation based on a mutex. Conclusion: - The BR2_ARCH_HAS_ATOMICS dependency is no longer needed. - We need to link with -latomic when gcc >= 4.7 is used. Note that reverse dependencies of icu are also changed accordingly. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/beecrypt: fix C++ support

2015-08-17T20:45:25+00:00

C++ support unconditionally needs shared libraries; it uses dlopen/dlsym. Also, fix the conditions under which the comment is shown. Finally, explicitly require C++ support when configuring. Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/*: rename patches according to the new policy

2015-02-03T13:52:56+00:00

Autogenerated from rename-patch.py (http://patchwork.ozlabs.org/patch/403345) Signed-off-by: Samuel Martin 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