From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] issue to build elfutils due to libintl
Date: Sat, 9 Mar 2019 22:08:18 +0100 [thread overview]
Message-ID: <20190309220818.7d373b55@gmx.net> (raw)
In-Reply-To: <20190309163432.GA25854@arthur-bzh>
Hello Arthur,
On Sat, 9 Mar 2019 17:34:32 +0100, Arthur LAMBERT <lambertarthur22@gmail.com> wrote:
> >
> > Did your run an complete build (make clean; make), see [1]?
> >
>
> Good suggestion. I did not try. I rerun the test with full clean and I have always the issue.
>
Mhhh, your defconfig builds fine here (on openSUSE Tumbleweed), maybe
try to build with 'make V=1' to gain more info (which compiler is used, which flags etc.)...
Here:
$ find . -name libintl.h
./build/uclibc-1.0.31/include/libintl.h
./build/uclibc-1.0.31/include/config/uclibc/has/libintl.h
./build/gettext-0.19.8.1/gettext-runtime/intl/libintl.h
./host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/libintl.h
So the missing libintl.h from your error message is available here...
Regards,
Peter
>
> My defconfig :
>
> BR2_arm=y
> BR2_cortex_a7=y
> BR2_ARM_FPU_NEON_VFPV4=y
> BR2_KERNEL_HEADERS_4_9=y
> BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
> BR2_PTHREAD_DEBUG=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_TARGET_GENERIC_HOSTNAME="femto"
> BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
> BR2_ENABLE_LOCALE_WHITELIST="en_US"
> BR2_TARGET_TZ_INFO=y
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_GIT=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="XXX"
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="XXX"
> BR2_LINUX_KERNEL_DEFCONFIG="XXX"
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="XXX"
> BR2_PACKAGE_LINUX_TOOLS_PERF=y
> BR2_PACKAGE_BUSYBOX_WATCHDOG=y
> BR2_PACKAGE_ALSA_UTILS=y
> BR2_PACKAGE_ALSA_UTILS_AMIXER=y
> BR2_PACKAGE_ALSA_UTILS_APLAY=y
> BR2_PACKAGE_ALSA_UTILS_SPEAKER_TEST=y
> BR2_PACKAGE_BZIP2=y
> BR2_PACKAGE_GETTEXT=y
> BR2_PACKAGE_DOSFSTOOLS=y
> BR2_PACKAGE_DOSFSTOOLS_FSCK_FAT=y
> BR2_PACKAGE_DOSFSTOOLS_MKFS_FAT=y
> BR2_PACKAGE_E2FSPROGS=y
> BR2_PACKAGE_E2FSPROGS_RESIZE2FS=y
> BR2_PACKAGE_MEMTOOL=y
> BR2_PACKAGE_PYTHON3=y
> BR2_PACKAGE_LIBSNDFILE=y
> BR2_PACKAGE_LIBVORBIS=y
> BR2_PACKAGE_LIBARCHIVE=y
> BR2_PACKAGE_OPENSSL=y
> BR2_PACKAGE_LIBCONFIG=y
> BR2_PACKAGE_DTC=y
> BR2_PACKAGE_DTC_PROGRAMS=y
> BR2_PACKAGE_LIBCURL=y
> BR2_PACKAGE_PAHO_MQTT_C=y
> BR2_PACKAGE_ELFUTILS=y
> BR2_PACKAGE_LIBUNWIND=y
> BR2_PACKAGE_OPENBLAS=y
> BR2_PACKAGE_PROTOBUF=y
> BR2_PACKAGE_PROTOBUF_C=y
> BR2_PACKAGE_BLUEZ5_UTILS=y
> BR2_PACKAGE_BLUEZ5_UTILS_CLIENT=y
> BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED=y
> BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL=y
> BR2_PACKAGE_DROPBEAR=y
> BR2_PACKAGE_GESFTPSERVER=y
> BR2_PACKAGE_IPTABLES=y
> BR2_PACKAGE_IPUTILS=y
> BR2_PACKAGE_IW=y
> BR2_PACKAGE_TCPDUMP=y
> BR2_PACKAGE_WIRELESS_TOOLS=y
> BR2_PACKAGE_WPA_SUPPLICANT=y
> BR2_PACKAGE_WPA_SUPPLICANT_AP_SUPPORT=y
> BR2_PACKAGE_WPA_SUPPLICANT_EAP=y
> BR2_PACKAGE_WPA_SUPPLICANT_HOTSPOT=y
> BR2_PACKAGE_WPA_SUPPLICANT_DEBUG_SYSLOG=y
> BR2_PACKAGE_WPA_SUPPLICANT_WPS=y
> BR2_PACKAGE_WPA_SUPPLICANT_CLI=y
> BR2_PACKAGE_WPA_SUPPLICANT_PASSPHRASE=y
> BR2_PACKAGE_HTOP=y
> BR2_TARGET_ROOTFS_TAR_GZIP=y
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BOARDNAME="xxxxx"
> BR2_TARGET_UBOOT_CUSTOM_GIT=y
> BR2_TARGET_UBOOT_CUSTOM_REPO_URL="xxxxx"
> BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xxxxx"
> BR2_TARGET_UBOOT_FORMAT_IMX=y
next prev parent reply other threads:[~2019-03-09 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 12:56 [Buildroot] issue to build elfutils due to libintl Arthur LAMBERT
2019-03-08 22:49 ` Peter Seiderer
2019-03-09 16:34 ` Arthur LAMBERT
2019-03-09 21:08 ` Peter Seiderer [this message]
2019-03-10 15:14 ` Arthur LAMBERT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190309220818.7d373b55@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox