Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: argus bind dmraid kismet libeXosip2 ltra etc...
Date: Mon, 26 Jan 2009 07:17:22 +0100	[thread overview]
Message-ID: <873af6d219.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090126003405.2EE7776D28@busybox.osuosl.org> (ulf@uclibc.org's message of "Mon\, 26 Jan 2009 00\:34\:04 +0000 \(UTC\)")

>>>>> "ulf" == ulf  <ulf@uclibc.org> writes:

 ulf> Author: ulf
 ulf> Date: 2009-01-26 00:34:02 +0000 (Mon, 26 Jan 2009)
 ulf> New Revision: 25041

 ulf> Log:
 ulf> Add help for packages without AVR32 support

Do they all really NEED avr32 patches to build? Some of them atleast
doesn't seem to be very hardware specific. Do they all fail doing
build for avr32? Can you post snippets of the build logs?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-26  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  0:34 [Buildroot] svn commit: trunk/buildroot/package: argus bind dmraid kismet libeXosip2 ltra etc ulf at uclibc.org
2009-01-26  6:17 ` Peter Korsgaard [this message]
2009-01-26 11:21   ` Ulf Samuelsson
2009-01-26 12:17     ` Peter Korsgaard
2009-01-26 12:27       ` Hans-Christian Egtvedt
2009-01-26 13:27         ` 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=873af6d219.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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