Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-11-23
Date: Thu, 24 Nov 2016 16:26:24 +0100	[thread overview]
Message-ID: <20161124152623.GH27313@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161124094429.4152c19b@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> Christian, Waldemar, Sam, Bernd, Alexey, Vlad, Vicente, J?rg, Fran?ois,
> please see below, there are some questions for you.
> 
> Summary of the build failures:
> 
>  - musl related:		8
>  - misc:			7
>  - static linking:		4
>  - PowerPC64le libtool:		2
>  - ARC related:			2
>  - uClibc-ng related:		1
>  - unknown:			1
> 
> So musl continues to be a pain to support, causing the biggest number
> of build failures...
> 
> On Thu, 24 Nov 2016 08:30:11 +0100 (CET), Thomas Petazzoni wrote:
> 
> >      powerpc |                   autossh-1.4e | NOK | http://autobuild.buildroot.net/results/08a458572a2e9c599dd32b837b1e5c02a6721973
> 
> unwind-dw2-fde-dip.c:465: undefined reference to `dl_iterate_phdr'
> 
> Waldemar, this is with uClibc-ng, and it seems like a relatively recent
> problem. Any idea?
> 

I thought it is a Xtensa specific issue, as now it happens for
PowerPC I need to dig deeper.
Strange that I couldn't reproduce it with OpenADK with uClibc-ng
1.0.19 and master.

best regards
 Waldemar

  reply	other threads:[~2016-11-24 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-23 Thomas Petazzoni
2016-11-24  8:44 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-11-24 15:26   ` Waldemar Brodkorb [this message]
2016-11-24 19:24   ` Jörg Krause
2016-11-24 19:58   ` Christian Stewart
2016-11-24 22:12   ` Jörg Krause
2016-11-25  0:22   ` Sam Bobroff
2016-11-25  8:09     ` Thomas Petazzoni
2016-11-25 10:47   ` Alexey Brodkin

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=20161124152623.GH27313@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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