Skip to contentSkip to conversation

dbus build fails since the bump of systemd to version 218

Buildroot Thierry Bultel 2 participants 4 messages Dec 12, 2014 – Dec 14, 2014

lore
Share & tools
lore
#0 lore raw

Hi,

Since the bump, there are undefined symbols when building dbus-1.8.10:

CCLD dbus-daemon
CCLD dbus-daemon-launch-helper
/shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status

Regards
Thierry

#1 lore raw
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thierry" == Thierry Bultel <[email protected]> writes:

Hi,
Since the bump, there are undefined symbols when building dbus-1.8.10:

Quoted 12 lines

CCLD dbus-daemon
CCLD dbus-daemon-launch-helper
/shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status

What toolchain is this? According to upstream it is could be because of a binutils bug:

https://www.marshut.net/kttspt/build-error-with-218-undefined-reference-to-start-bus-error-map.html

Signature · 1 line
Bye, Peter Korsgaard
#2 lore raw

Le 13/12/2014 22:48, Peter Korsgaard a ?crit :

Quoted 18 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thierry" == Thierry Bultel <[email protected]> writes:

Hi,
Since the bump, there are undefined symbols when building dbus-1.8.10:

Quoted 12 lines

CCLD dbus-daemon
CCLD dbus-daemon-launch-helper
/shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__stop_BUS_ERROR_MAP' /shared/buildroot_community/buildroot/output/host/usr/i586-buildroot-linux-gnu/sysroot/usr/lib/libsystemd.so:
undefined reference to `__start_BUS_ERROR_MAP'
collect2: error: ld returned 1 exit status

Quoted 5 lines

What toolchain is this? According to upstream it is could be because of a binutils bug:

https://www.marshut.net/kttspt/build-error-with-218-undefined-reference-to-start-bus-error-map.html

This happens with buildroot toolchain, eglibc 2.18, gcc-4.8.x, binutils 2.22

It does not happen with binutils-2.23.2 and binutils-2.24

#3 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thierry" == Thierry Bultel <[email protected]> writes:

Hi,

Quoted 8 lines
Quoted 4 lines

What toolchain is this? According to upstream it is could be because of a binutils bug:

https://www.marshut.net/kttspt/build-error-with-218-undefined-reference-to-start-bus-error-map.html

This happens with buildroot toolchain, eglibc 2.18, gcc-4.8.x, binutils 2.22 It does not happen with binutils-2.23.2 and binutils-2.24

Ok, thanks for investigating it. It won't fix it for external toolchains, but perhaps it is time to bump our default binutils version to 2.24?

Signature · 2 lines
Venlig hilsen,
Peter Korsgaard