Provide the path to HOST_DIR for libxml, libxslt and libiconv like for the target variant to avoid a build issue on host where /bin is a symlink to /usr/bin. Indeed, the configure script use a custom m4 macro XSTAR_LIB_CHECK to find xml2-config: XSTAR_LIB_CHECK([LIBXML], [xml2-config]) This macro come from a local m4 file m4/xstar-check-libs.m4 where it use: AC_PATH_PROG(LIBXXX()_CONFIG, xxx_config(), [], [$LIBXXX()_PREFIX/bin$PATH_SEPARATOR$PATH] Since no prefix seems to be defined by $LIBXXX()_PREFIX, AC_PATH_PROG look by itself at /bin/ for xml2-config. So the PATH variable set by Buildroot containing HOST_DIR/bin is ignored. The wrong xml2-config is used during the build and the build fail when no xml2 headers are installed on the host. Fixes: src/xml_C14N.c:12:31: fatal error : libxml/xmlversion.h : No such file or directory #include <libxml/xmlversion.h> ^ In file included from src/trans.c:4:0: src/trans.h:32:30: fatal error : libxml/xmlmemory.h : No such file or directory #include <libxml/xmlmemory.h> Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: remove french messages from the commit log, drop --with-libiconv-prefix option, since we don't have a libiconv dependency for the host.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.defconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitlab-ci.yml.in | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
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. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches