buildroot/package/libupnpp, branch 2017.05

package/l*/Config.in: fix ordering of statements

2017-05-01T09:51:23+00:00

The check-package script when ran gives warnings on ordering issues on all of these Config files. This patch cleans up all warnings related to the ordering in the Config files for packages starting with the letter l in the package directory. The appropriate ordering is: type, default, depends on, select, help See http://nightly.buildroot.org/#_config_files for more information. Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

boot, linux, package: use SPDX short identifier for GPLv2/GPLv2+

2017-04-01T13:16:38+00:00

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

package/libupnpp: bump to version 0.15.1

2016-10-12T11:57:52+00:00

Remove patches applied upstream. No need to set AUTORECONF anymore. Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni

package/libupnpp: add patch to get pkg-config file

2016-09-17T11:33:30+00:00

Apply a patch from upstream to install a pkg-config file for libupnpp. Fetch from: https://github.com/medoc92/libupnpp/commit/9f03bb0e7b47e2843edea6f25ed9eabbfb6412df Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni

package/libupnpp: add patch to fix build issue

2016-09-13T19:27:35+00:00

Bumping libupnpp to version 0.15.0 introduced a build error for some architectures: ``` ./libupnpp/workqueue.h:308:29: error: field 'res' has incomplete type std::future res; ^ ./libupnpp/workqueue.h: In member function 'bool WorkQueue::start(int, void* (*)(void*), void*)': ./libupnpp/workqueue.h:81:25: error: invalid use of incomplete type 'class std::packaged_task' w.res = task.get_future(); ``` The problem is that `std::future` is not available for all architectures, e.g. it is missing for ARMv5 (soft-float). libstdc++ enables `std::future` only if `ATOMIC_INT_LOCK_FREE > 1`, which according the the libstdc++ documentation means that operations on atomic ints are guaranteed to be lock-free. This check is not true for some target, e.g. the toolchain for the ARMv5 target defines: ``` $ echo | /usr/bin/arm-linux-g++ -dM -E - | grep ATOMIC_INT_LOCK_FREE #define __GCC_ATOMIC_INT_LOCK_FREE 1 ``` We add a patch from upstream which detects if `std::future` is available and opts-out the functionality for unsupported targets. Fixes: http://autobuild.buildroot.net/results/f8eb38ef79160e1f646dae0be19f27fae82a58bc http://autobuild.buildroot.net/results/158e0ceeff009146b78a0d2bb278c76479bafc34 http://autobuild.buildroot.net/results/1760cf53c77e16bb2b5bc795bd0ce5eb65f258f2 http://autobuild.buildroot.net/results/5b73e52495aa1bbb2c704492237da784b9d74bc2 http://autobuild.buildroot.net/results/6d922a1bbace024fcf040beb49bbb119036865ef http://autobuild.buildroot.net/results/bebb8983e7579ee4b4bcf18f037c7797ab86f8db http://autobuild.buildroot.net/results/0f1a5832ced2a6ec2e18f9f14197446fda6af692 http://autobuild.buildroot.net/results/94a9cc349f23a47246b06619a019bcb917493415 http://autobuild.buildroot.net/results/19fba094098af5c1ce1e1371e5e88393c4a6ac9c http://autobuild.buildroot.net/results/578935b5c04005d1f096059387d16911f953ec6f http://autobuild.buildroot.net/results/2ad698f1665b7b886141672181cb76ec3c40a743 and more... Note, that we enable autoreconf as the patch touches configure.ac. Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni

package/libupnpp: bump to version 0.15.0

2016-09-11T13:34:51+00:00

Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni

package: remove _gp issue workaround for Codesourcery nios2 toolchain

2016-03-05T18:11:29+00:00

The _gp link issue has been fixed in CS nios2 2015.11. Signed-off-by: Romain Naour Signed-off-by: Thomas Petazzoni

package/libupnpp: bump to version 0.14.1

2016-02-19T15:33:13+00:00

Signed-off-by: Jörg Krause Signed-off-by: Peter Korsgaard

package/libupnpp: needs at least gcc 4.6

2016-01-05T10:50:16+00:00

Version 0.13.1 of libupnpp uses range-based for loops. This C++11 feature requires at least gcc 4.6. Fixes: http://autobuild.buildroot.net/results/aa9/aa93ff96305a3b201636bea65f1cfdb6db6d3dfb/ http://autobuild.buildroot.net/results/d8b/d8b96987a5336a64857817ec9831b0fb12867e7c/ http://autobuild.buildroot.net/results/408/40807fe84f67961817b6592a6df243c036cf3b4b/ http://autobuild.buildroot.net/results/408/40807fe84f67961817b6592a6df243c036cf3b4b/ .. and many more Signed-off-by: Jörg Krause Signed-off-by: Peter Korsgaard

package/libupnpp: bump to version 0.13.1

2015-12-26T15:15:28+00:00

Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni