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] [autobuild.buildroot.net] Your build results for 2017-02-15
Date: Thu, 16 Feb 2017 11:11:20 +0100	[thread overview]
Message-ID: <20170216111120.107a7a61@free-electrons.com> (raw)
In-Reply-To: <20170216102154.4f896bea@free-electrons.com>

Hello,

On Thu, 16 Feb 2017 10:21:54 +0100, Thomas Petazzoni wrote:

> commit a44d7f2dbb19a54a8f2beb5c0f0adb0680999319
> Author: Waldemar Brodkorb <wbx@openadk.org>
> Date:   Sun Dec 4 12:20:27 2016 +0100
> 
>     uclibc: update to 1.0.20
>     
>     The test suite is removed from the package and is already a separate
>     package in buildroot. All patches are upstream, so remove them.
>     The UCLIBC_HAS_LFS option is removed upstream.
>     
>     Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
>     [Thomas: remove BR2_UCLIBC_INSTALL_TEST_SUITE option, add it to
>     Config.in.legacy.]
>     Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Seems like the story is more complicated. I did a build of czmq right
before the uClibc bump to 1.0.20, and right after, and both builds were
successful.

Two options:

 - This commit is not the culprit.

 - My simple configuration with just czmq doesn't trigger the problem,
   and it's only czmq with some optional dependencies that triggers the
   problem.

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

  reply	other threads:[~2017-02-16 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170216072900.AAE4920BC6@mail.free-electrons.com>
     [not found] ` <CALdGskKtWsQOyKehenpwZHyaMuYHQ600kiMr4w080DNYGRcBKQ@mail.gmail.com>
2017-02-16  9:21   ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-02-15 Thomas Petazzoni
2017-02-16 10:11     ` Thomas Petazzoni [this message]
2017-02-16 19:14       ` Waldemar Brodkorb
2017-02-16 21:15         ` Thomas Petazzoni
2017-02-17  7:13           ` Waldemar Brodkorb
2017-02-17  9:32             ` Thomas Petazzoni

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=20170216111120.107a7a61@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