a0a244d26d
Fixes: http://autobuild.buildroot.net/results/256/2561190b274d71666c4bdf3c569b02063cefdb30/ http://autobuild.buildroot.net/results/14e/14e6addcd3ec35f882da7ec489caa9b60ecd4b63/ http://autobuild.buildroot.net/results/cf0/cf011286be839674d358a8bccaf1c5c52de75e46/ madplay needs gettext when built with nls, and it support 3 variants: - C library support gettext (E.G. glibc) - Libintl (E.G. uClibc) - An included libintl copy The included libintl copy has unfortunately bitrotted and doesn't even build any more. With that said, musl DOES have gettext support, so that should be used instead. The configure script unfortunately uses an old AM_GNU_GETTEXT test, which explicitly checks for nonstandard glibc extensions, which musl doesn't support: http://www.openwall.com/lists/musl/2015/04/16/3 Which causes the detection to fail: configure:24770: checking for GNU gettext in libc configure:24794: /home/peko/source/buildroot/output/host/usr/bin/i486-linux-musl-gcc \ -o conftest -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 \ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5 /tmp/ccboDFhK.o: In function `main': conftest.c:(.text+0x39): undefined reference to `_nl_msg_cat_cntr' conftest.c:(.text+0x40): undefined reference to `_nl_domain_bindings' collect2: error: ld returned 1 exit status Now, madplay itself doesn't actually use these glibc extensions, so just force the detection of GNU gettext when musl is used. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| .defconfig | ||
| .gitignore | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC.