buildroot/package/iprutils, branch 2017.02

ncurses: remove BR2_PACKAGE_NCURSES_TARGET_{FORM, MENU, PANEL} options

2017-02-26T16:00:12+00:00

The ncurses sub-options BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL} are currently very badly broken: they only control whether the libform, libmenu and libpanel libraries are installed in $(TARGET_DIR), but do absolutely nothing about their installation in $(STAGING_DIR). This means that when one of those options is disabled, the corresponding library is indeed not installed in the target, but is available in staging. It can therefore be detected by the configure script of another package and used... even though the library will not be in the target, causing a runtime failure. Internally, ncurses.mk uses the "make install" logic of ncurses for the staging installation, but uses a completely hand-written logic for the target installation, which is the reason for this desynchronization between what's installed in staging and target. When BR2_PACKAGE_NCURSES_WCHAR=y, this also causes some build failures. Indeed, when BR2_PACKAGE_NCURSES_WCHAR=y, Buildroot creates some symbolic links lib.so -> libw.so in staging and target, but only for the lib that have been enabled by BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL}. Due to this, a package that for example needed the libmenu library but forgot to select BR2_PACKAGE_NCURSES_TARGET_MENU was: - Building fine with BR2_PACKAGE_NCURSES_WCHAR disabled (because libmenu.so exists in staging), but would fail to run at runtime because libmenu.so is not in the target. - Fail to build with BR2_PACKAGE_NCURSES_WCHAR=y because only libmenuw.so exists, and not the libmenu.so symbolic link. Since those libraries are small (43K for libform, 21K for libmenu and 8.2K for libpanel), this commit takes the very simple approach of removing those options, and installing the libraries unconditionally. It therefore uses the "make install" logic for both the staging *and* target installation. In detail, this commit: - Removes the NCURSES_PROGS variable, not needed since --without-progs already allows to disable the build and installation of programs. - Removes the NCURSES_LIBS-y variable, and replaces it with a single unconditional assignement to NCURSES_LIBS, only used to create the libw.so -> lib.so symbolic links when wchar support is enabled. - Removes NCURSES_INSTALL_TARGET_CMDS and the functions it was calling: NCURSES_INSTALL_TARGET_LIBS and NCURSES_INSTALL_TARGET_PROGS. - Adds a NCURSES_TARGET_SYMLINK_RESET hook to create the reset -> tset symbolic link, as was done before. - Adds a NCURSES_TARGET_CLEANUP_TERMINFO to cleanup the terminfo files in the target, so that we stay in the same situation in terms of installed terminfo files. - Removes the BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL} options from the Config.in files: both their definition and usage. - Simplifies all the symlink dance for lib -> libw, because as Yann E. Morin suggested, this dance is only needed in staging, not in the target. Once binaries have been built, they refer to the SONAME of the library, which is the libw variant (for shared linking). For static linking and .pc files, it's obvious that we don't care about them on the target. Therefore the NCURSES_LINK_LIBS_STATIC, NCURSES_LINK_LIBS_SHARED and NCURSES_LINK_PC functions no longer take any argument: they always apply to STAGING_DIR only. NCURSES_LINK_TARGET_LIBS is removed. It is worth mentioning that adding Config.in.legacy support is *NOT* necessary. Indeed: - If they were disabled before this patch, having them in Config.in.legacy would not trigger the legacy warning. - If they were enabled before this patch, then the behavior is unchanged: all libraries are now unconditionally installed. So there is no point in warning the user. We double-checked the installed size of a filesystem containing just ncurses before and after this patch, and the only folder that has its size changed is /usr/lib, growing from 852 KB to 932 KB in the wchar enabled case. That's a 80 KB system size increase. This commit fixes the sngrep build failure and potentially numerous runtime issues with ncurses. Fixes: http://autobuild.buildroot.net/results/7b5db21a6c568e6c6c8fe2b5d5a2f5ca24df510c/ Signed-off-by: Thomas Petazzoni

iprutils: uses fork(), needs MMU

2016-07-03T11:17:35+00:00

Fixes: http://autobuild.buildroot.net/results/6ee89f9a4e05c89375a96ac7085747afc301b896/ Signed-off-by: Thomas Petazzoni

package/iprutils: add patch to fix musl build

2016-02-07T13:14:03+00:00

This commit adds a patch to the iprutils to fix the build with the musl C library. Signed-off-by: Bernd Kuhls [Thomas: reformatted the patch with Git, added a better commit log.] Signed-off-by: Thomas Petazzoni

package/iprutils: bump version to 2.4.10

2016-02-07T12:57:22+00:00

Upstream now provides a new autoconf-based build system, therefore our patches for Makefile are not needed anymore. We adapt the gettext patch to make sure that the configure script doesn't check for libintl.h, and we add an additional patch to fix the libm check. Signed-off-by: Bernd Kuhls [Thomas: rework patches.] Signed-off-by: Thomas Petazzoni

iprutils: drop unneeded ncurses5-config handling

2015-02-03T14:59:57+00:00

ncurses nowadays installs the headers directly into $prefix/usr/include, so ncurses5-config doesn't return anything important and the logic wasn't taking the wchar variant into consideration - So just drop it. 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

iprutils: bump to version 2.4.5

2014-12-14T19:47:31+00:00

Rebase patch 0003 on top of 2.4.5 release. Signed-off-by: Romain Naour Signed-off-by: Peter Korsgaard

iprutils: use correct include path for ncurses

2014-12-14T19:47:20+00:00

The Makefile is hardcoded for /usr/include/ncurses, so override it. Signed-off-by: Peter Korsgaard Reported-by: Romain Naour

iprutils: rename patches to follow the new name convention

2014-12-14T18:55:17+00:00

Signed-off-by: Romain Naour Signed-off-by: Peter Korsgaard

iprutils: Fix static build by passing the libraries in the right order

2014-09-21T17:47:47+00:00

This mistake was causing failures like this one: m_post.c:(.text+0x60): undefined reference to `wattr_on' Patch sent upstream: https://sourceforge.net/p/iprdd/iprutils/merge-requests/1/ Fixes: http://autobuild.buildroot.net/results/500/5004e7b230635e0605acdd17d2b7d2d01fc5075c/ Signed-off-by: Vicente Olivert Riera Tested-by: Gustavo Zacarias Acked-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni