From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] dbus build fails since the bump of systemd to version 218
Date: Sat, 13 Dec 2014 22:48:41 +0100 [thread overview]
Message-ID: <87wq5vp6fa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <548B6E4E.104@free.fr> (Thierry Bultel's message of "Fri, 12 Dec 2014 23:38:06 +0100")
>>>>> "Thierry" == Thierry Bultel <tbultel@free.fr> writes:
> 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
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
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-12-13 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 22:38 [Buildroot] dbus build fails since the bump of systemd to version 218 Thierry Bultel
2014-12-13 21:48 ` Peter Korsgaard [this message]
2014-12-14 10:14 ` Thierry Bultel
2014-12-14 12:18 ` Peter Korsgaard
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=87wq5vp6fa.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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