Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-10-03
Date: Thu, 24 Oct 2019 10:21:01 +0200	[thread overview]
Message-ID: <20191024102101.176e7b01@windsurf> (raw)
In-Reply-To: <1gm78gx84n.ln2@ID-313208.user.individual.net>

On Thu, 24 Oct 2019 06:38:57 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:

> bug is also present on master branch
> 
> http://autobuild.buildroot.net/results/d8e/
> d8e8c658476c4d51b9fd13021b293b1890292620/
> 
> and is fixed by a patch which is part of this series:
> 
> http://patchwork.ozlabs.org/project/buildroot/list/?series=133684

Unfortunately, it is not "fixed", but worked around, and the proper fix
is in elf2flt, to make it support those relocation types.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-10-24  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  6:17 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-10-03 Thomas Petazzoni
2019-10-24  4:38 ` Bernd Kuhls
2019-10-24  8:21   ` Thomas Petazzoni [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=20191024102101.176e7b01@windsurf \
    --to=thomas.petazzoni@bootlin.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