Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: update to 1.0.21
Date: Thu, 29 Dec 2016 09:31:09 +0100	[thread overview]
Message-ID: <20161229093109.404db8da@free-electrons.com> (raw)
In-Reply-To: <20161226192948.GA11926@waldemar-brodkorb.de>

Hello,

On Mon, 26 Dec 2016 20:29:48 +0100, Waldemar Brodkorb wrote:
> Remove all patches as they are upstream.
> Remove MALLOC_GLIBC_COMPAT and UCLIBC_HAS_OBSTACK as they got removed.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>

I believe this update breaks the libglib build. The new uclibc-ng
version provides its own libiconv implementation. And interestingly,
all the libglib failures of the last days occur only with the uClibc
internal toolchain configurations (on powerpc, arm, xtensa and arc).
And they all fail with:

  gconvert.c:25:19: fatal error: iconv.h: No such file or directory

So it seems like the configure script detects that the C library
provides iconv_open() and therefore assumes it provides the iconv
implementation. But then later fails because there's no iconv.h.

Note: this is a very quick analysis, the problem may be more
complicated. But it clearly points at the latest uClibc-ng bump.

Full list of build failures:

   http://autobuild.buildroot.net/?reason=libglib2-2.50.2&step=250

It started failing at commit b575baeb, which is exactly one commit
after the uclibc-ng bump to 1.0.21.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2016-12-29  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 19:29 [Buildroot] [PATCH] uclibc: update to 1.0.21 Waldemar Brodkorb
2016-12-27  9:37 ` Peter Korsgaard
2016-12-29  8:31 ` 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=20161229093109.404db8da@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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