Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] dbus build fails since the bump of systemd to version 218
Date: Sun, 14 Dec 2014 13:18:13 +0100	[thread overview]
Message-ID: <87k31upgqi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <548D6323.3010102@free.fr> (Thierry Bultel's message of "Sun, 14 Dec 2014 11:14:59 +0100")

>>>>> "Thierry" == Thierry Bultel <tbultel@free.fr> writes:

Hi,

 >> 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?

-- 
Venlig hilsen,
Peter Korsgaard 

      reply	other threads:[~2014-12-14 12:18 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
2014-12-14 10:14   ` Thierry Bultel
2014-12-14 12:18     ` Peter Korsgaard [this message]

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=87k31upgqi.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