From: Douglas RAILLARD <public.douglas.raillard@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix elf2flt build
Date: Thu, 27 Aug 2015 23:00:45 +0200 [thread overview]
Message-ID: <5061538.Liz3OFzo4L@raillard-dv6> (raw)
In-Reply-To: <20150827203501.00528bd2@free-electrons.com>
Thomas,
> Thanks for this patch. Great to see that there is some interest in
> noMMU architecture. Which architecture are you working on?
Im actually working on the STM32F429 Cortex M4 with the
stm32f429-discovery board from STMicroelectronics.
It seems that things are also moving on the kernel side
for this arch and board.
> I'm not able to reproduce the problem: here host-elf2flt builds fine.
I did not find any failure for elf2flt on the autobuild server,
but without the patch, make complains.
I have not checked if libbfd can be configured without plugin
support, but it fails with my configuration
(sorry for untranslated french diagnostic error):
/usr/bin/gcc -Wall -O2 -I/working_dir/buildroot/output/host/usr/include -
L/working_dir/buildroot/output/host/lib -
L/working_dir/buildroot/output/host/usr/lib -Wl,-
rpath,/working_dir/buildroot/output/host/usr/lib -o elf2flt elf2flt.o
compress.o stubs.o -lc -lz /working_dir/buildroot/output/build/host-
binutils-2.24/bfd/libbfd.a /working_dir/buildroot/output/build/host-
binutils-2.24/libiberty/libiberty.a -lz
/working_dir/buildroot/output/build/host-binutils-2.24/bfd/libbfd.a(plugin.o):
in fonction ? try_load_plugin ?:
plugin.c:(.text+0x1db): undefined reference to ? dlopen ?
plugin.c:(.text+0x1f1): undefined reference to ? dlsym ?
plugin.c:(.text+0x270): undefined reference to ? dlerror ?
collect2: error: ld a retourn? 1 code d'?tat d'ex?cution
Makefile:75 : la recette pour la cible ? elf2flt ? a ?chou?e
make[1]: *** [elf2flt] Erreur 1
make[1] : on quitte le r?pertoire ? /working_dir/buildroot/output/build/host-
elf2flt-21c6a41885ad544763ccd19883c1353f3b0b7a47 ?
> However the build of an ARM Cortex-M3 toolchain fails during the uClibc
> build (which takes place *after* host-elf2flt is built).
There are indeed problems when some toolchain options are selected,
so I managed to leave them out for the moment to focus on getting
something built. Here is my buildroot configuration generated with
make savedefconfig:
BR2_arm=y
BR2_cortex_m3=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_GLOBAL_PATCH_DIR="../patch"
BR2_UCLIBC_VERSION_0_9_33=y
BR2_UCLIBC_CONFIG="package/uclibc/uClibc-ng.config"
BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PTHREADS_NONE=y
BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
BR2_GCC_ENABLE_LTO=y
BR2_PACKAGE_HOST_ELF2FLT=y
BR2_PACKAGE_HOST_GDB=y
BR2_PACKAGE_HOST_GDB_TUI=y
BR2_PACKAGE_HOST_GDB_PYTHON=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="master"
BR2_LINUX_KERNEL_DEFCONFIG="stm32"
BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y
BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="xipImage"
BR2_TARGET_ROOTFS_ROMFS=y
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="stm32f429-discovery"
BR2_PACKAGE_HOST_UBOOT_TOOLS=y
Moreover, there are some other issues with elf2flt when the toolchain is built
(one of the first target binary which get compiled after uClibc is getconf,
part of uClibc I guess),
I am writing another email for that
Regards,
Douglas
Le jeudi 27 ao?t 2015 20:35:01, vous avez ?crit :
> Douglas,
>
> On Thu, 27 Aug 2015 18:47:17 +0200, Douglas RAILLARD wrote:
> > Add -ldl to fix elf2flt build, because libbfd
> > uses dlopen and friends for plugin loading
> >
> > Signed-off-by: Douglas RAILLARD <public.douglas.raillard@gmail.com>
>
> Thanks for this patch. Great to see that there is some interest in
> noMMU architecture. Which architecture are you working on?
>
> I'm not able to reproduce the problem: here host-elf2flt builds fine.
> However the build of an ARM Cortex-M3 toolchain fails during the uClibc
> build (which takes place *after* host-elf2flt is built).
>
> Thanks!
>
> Thomas
--
Douglas RAILLARD
next prev parent reply other threads:[~2015-08-27 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 16:47 [Buildroot] [PATCH 1/1] Fix elf2flt build Douglas RAILLARD
2015-08-27 18:35 ` Thomas Petazzoni
2015-08-27 21:00 ` Douglas RAILLARD [this message]
[not found] ` <6966330.pLhB8QsgjT@raillard-dv6>
2015-08-28 8:09 ` Thomas Petazzoni
2015-08-28 10:17 ` Douglas RAILLARD
2015-08-28 11:20 ` Thomas Petazzoni
2015-08-28 13:01 ` Waldemar Brodkorb
2015-08-30 15:43 ` Douglas RAILLARD
2015-08-31 6:05 ` Waldemar Brodkorb
2015-08-31 12:08 ` Douglas RAILLARD
2015-08-31 12:28 ` Thomas Petazzoni
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=5061538.Liz3OFzo4L@raillard-dv6 \
--to=public.douglas.raillard@gmail.com \
--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