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] Recurrent Blackfin build failure on icu
Date: Wed, 29 May 2013 21:35:10 +0200	[thread overview]
Message-ID: <20130529213510.43fc1372@skate> (raw)

Hello Sonic,

On our autobuilders, a number of Blackfin builds end up failing with a
problem on the icu package, which otherwise seems to build fine on
other architectures.

See
http://autobuild.buildroot.org/results/0f9/0f953610792aa75f9bb1f9218bcac27b2786e3f8/build-end.log
for one occurrence of this problem. It would be nice if you could have
a look and figure out a way of solving this build problem.

Generally speaking, would you be interested in receiving a daily e-mail
that contains the list of build failures that occurred on the previous
day, and that are related to the Blackfin architecture? Supporting an
architecture in Buildroot also means to have this architecture in a
good shape in terms of autobuilders testing.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2013-05-29 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 19:35 Thomas Petazzoni [this message]
2013-06-03  9:26 ` [Buildroot] Recurrent Blackfin build failure on icu Sonic Zhang
2013-06-03  9:38   ` Thomas Petazzoni
2013-06-06  2:32     ` Sonic Zhang
2013-06-06  6:07       ` Thomas Petazzoni
2013-06-20 23:21       ` Mike Frysinger
2013-06-21  6:38         ` 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=20130529213510.43fc1372@skate \
    --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