Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool error with AVR32
Date: Fri, 28 Sep 2007 21:29:13 +0200	[thread overview]
Message-ID: <20070928192912.GU20951@aon.at> (raw)
In-Reply-To: <d6cda7730709281217l6b6b770dqd72a42ca687e9bba@mail.gmail.com>

On Fri, Sep 28, 2007 at 08:17:18PM +0100, Thiago A. Corr?a wrote:
>On 9/28/07, Ivan Kuten <ivan.kuten@promwad.com> wrote:

>> Also it would be useful to create something like this "http://kegel.com/crosstool/crosstool-0.43/buildlogs/"
>> but for package/target status.
>
>I was trying to setup a buildbot for buildroot/avr32 but then had to
>put out some fires and didn't had the time to go back to manual
>reading/etc.... I was trying to setup a buildmaster, but if someone
>closer to the project would like to setup an official buildmaster, I
>would gladly join as a buildbot.

IIRC we already have a buildbot for uClibc. Not sure how loaded the
participants are, though.

  reply	other threads:[~2007-09-28 19:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 18:17 [Buildroot] Libtool error with AVR32 don
2007-09-27 20:53 ` Ulf Samuelsson
2007-09-27 22:19   ` don
2007-09-27 22:34     ` Bernhard Fischer
2007-09-27 23:42       ` Ulf Samuelsson
2007-09-28 16:09       ` don
2007-09-28 16:38         ` Ulf Samuelsson
2007-09-28 18:34           ` don
2007-09-28 16:51         ` Bernhard Fischer
2007-09-28 19:06           ` Ulf Samuelsson
2007-09-28 19:42           ` Ivan Kuten
2007-09-28 19:17             ` Thiago A. Corrêa
2007-09-28 19:29               ` Bernhard Fischer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-14 20:09 don
2007-10-14 23:34 ` Ivan Kuten
2007-10-15  3:47   ` don

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=20070928192912.GU20951@aon.at \
    --to=rep.dot.nop@gmail.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