summaryrefslogtreecommitdiffstats
path: root/package/net-tools/0001-Makefile-fix-static-linking-issue-with-lintl.patch
Commit message (Collapse)AuthorAgeFilesLines
* net-tools: remove libintl static linking handlingThomas Petazzoni2017-07-051-79/+0
| | | | | | | | | | | | | | | | | We no longer support building the full-blown libintl in static linking scenarios, as it causes too many problems. Patch 0001-Makefile-fix-static-linking-issue-with-lintl.patch was added to allow passing -lintl through LIBS, in a place that works for static linking. However, for dynamic linking, we can simply pass -lintl through the existing LDFLAGS variable, as it was done prior to commit 38bfd129c64a9cfd82c4fa4c797afadf12a6ffaa ("package/net-tools: fix static linking issue with lintl"). This commit does that and gets rid of the now useless patch. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/net-tools: fix static linking issue with lintlRomain Naour2016-05-311-0/+79
When net-tools are build with uClibc-ng and statically linked, some tools like hostname and route needs to link with -lintl. Adding -lintl in LDFLAGS place the library before object files: arm-linux-gcc -O2 -g -Wall -fno-strict-aliasing -static -lintl -Llib -o hostname hostname.o Add $(LIBS) after object files in the Makefile to place -lintl correctly. Rework NET_TOOLS_BUILD_CMDS to set LDFLAGS with only TARGET_LDFLAGS and set LIBS with -lintl when needed. Fixes: http://autobuild.buildroot.net/results/134/1345b6d366125320b89512e7ce7f142f1a03acf8 Ref: http://lists.busybox.net/pipermail/buildroot/2016-May/162216.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
OpenPOWER on IntegriCloud