All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain/gcc: the ARC version of gcc needs host-flex/host-bison
Date: Fri, 10 May 2013 17:53:31 +0200	[thread overview]
Message-ID: <20130510175331.0e6917aa@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D6339FF18A@de02wembxa.internal.synopsys.com>

Dear Mischa Jonker,

On Fri, 10 May 2013 14:47:56 +0000, Mischa Jonker wrote:

> Thank you for fixing this. Is there any way I can sort the autobuilder results so that I can see specific build problems for ARC?

Not as of today, you can't filter the results. I'm working on doing
this. I started doing something in Python/Django, but had some issues,
so I guess I'll continue with the PHP stuff we're already using, and
improve it to be able to sort things.

In the mean time, I often monitor the autobuilder results, so if
there's anything ARC related, I'll notify you.

Best regards,

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-10 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 15:53 [Buildroot] [PATCH 1/2] toolchain/gcc: make sure to pass $(HOST_DIR)/usr/bin in the PATH Thomas Petazzoni
2013-05-09 15:53 ` [Buildroot] [PATCH 2/2] toolchain/gcc: the ARC version of gcc needs host-flex/host-bison Thomas Petazzoni
2013-05-10 14:47   ` Mischa Jonker
2013-05-10 15:53     ` Thomas Petazzoni [this message]
2013-05-13 21:40     ` Thomas Petazzoni
2013-05-12 20:22 ` [Buildroot] [PATCH 1/2] toolchain/gcc: make sure to pass $(HOST_DIR)/usr/bin in the PATH Peter Korsgaard

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=20130510175331.0e6917aa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.