buildroot/package/setools, branch 2016.08

setools: fix build with latest selinux libraries

2016-07-01T09:06:37+00:00

Setools 3.3.8 won't cleanly compile against newer versions of the new selinux libraries. This patch fixes these errors. Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

libselinux: bump to version 2.5

2016-07-01T09:06:05+00:00

In addition, if a user is using glibc 2.22, the default CFLAG D_FILE_OFFSET_BITS=64 will cause a compile error. This flag is now removed from the CFLAGS in the make file to ensure that toolchains compiled against glibc 2.22 will build the new version of the package properly. In addition, libselinux now uses fts(), which is not available on musl, and not provided by our default uClibc configuration. Therefore, libselinux now depends on glibc, as well as all its reverse dependencies. Signed-off-by: Adam Duskett Reviewed-by: "Yann E. MORIN" [Thomas: add glibc dependency for fts().] Signed-off-by: Thomas Petazzoni

setools: fix build on SPARC64

2016-03-26T17:49:41+00:00

To build shared libraries on SPARC64, -fPIC must be used instead of just -fpic. This commit fixes the setools package, which allows to get rid of the following autobuilder failure: http://autobuild.buildroot.net/results/ba1e473178bb66ebc43897b20e534606d2577ee3/ Signed-off-by: Thomas Petazzoni

package/setools: add homepage to Config.in

2016-01-26T21:33:04+00:00

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

setools: comma separate licenses

2015-12-15T21:04:53+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

package: Remove trailing slash from all package site URLs

2015-09-30T10:46:42+00:00

The recommended form is without the trailing slash, and will become mandatory in a coming commit. This avoids the need for the $$($(2)_SITE:/=) magic in package/pkg-generic.mk to avoid double slashes in download URLs, like "https://mosh.mit.edu//mosh-1.2.5.tar.gz". ^^ Note: this work has already been done in b0b9606530dfc6de4030 a few months ago and earlier in c7f4b964718bc5a3329b and 4a9eb20de817fa64, but no check has been added at that time to avoid new slashes to slip in, and so they did. This time a patch will follow immediately to prevent future mistakes from being unnoticed. Mass-replaced with the following command: git grep -l '_SITE.*/$' | xargs sed -i '/_SITE.*=/s|/$||' Signed-off-by: Luca Ceresoli Signed-off-by: Thomas Petazzoni

setools: depends on host-flex

2015-09-30T08:15:40+00:00

setools needs host-flex in order to generate some source files during build time, otherwise it will fail with an error like this one: error: policy_scan.c: No such file or directory Issue reported here as a race condition problem, but it turned out that it the actual problem was the lack of host-flex: https://github.com/TresysTechnology/setools3/issues/5#issuecomment-144048612 Fixes: http://autobuild.buildroot.net/results/dad/dad9d79c10722b203536540141a6defc79937e4e/ Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

Revert "setools: fix race condition"

2015-09-30T08:15:27+00:00

This reverts commit 1ac68fe2c9b4cea91c7a30429ebf75279ede8e70. Further investigations revealed that the problem wasn't a race condition but the lack of flex package in the host machine: https://github.com/TresysTechnology/setools3/issues/5#issuecomment-144048612 Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

setools: fix race condition

2015-09-10T20:07:30+00:00

As reported upstream: https://github.com/TresysTechnology/setools3/issues/5 setools tries to compile a .c file before being generated and then it produces an error like this one: error: policy_scan.c: No such file or directory Until upstream fixes the problem we can workaround this by using MAKE1 as the SETOOLS_MAKE. Fixes: http://autobuild.buildroot.net/results/119/1196ac448c77320b59b63b6133d2d1af1245bf69/ Signed-off-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

package/setools: needs wchar

2015-08-29T10:43:17+00:00

Even though setools itself does not require wide chars, the configure script needs them when testing for C99 support. Since: - it is not clear whether wchar are mandatory for C99 or not, - only uClibc may miss support for wide chars, - using SELinux would probably involve rather big systems (i.e. glibc would not be such a huge overhead), just make setools depend on the toolchain having widechar. Fixes: http://autobuild.buildroot.org/results/051/051a7f72ebadd56407700c22b57e942f08eb1c09/ http://autobuild.buildroot.org/results/a4b/a4b2a6f1920430af43c23239de17200e70951b3b/ ... Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Matt Weber Cc: Clayton Shotwell Signed-off-by: Thomas Petazzoni