Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] at91sam9g20dfc_defconfig doesn't build (Grant Edwards)
Date: Tue, 5 Jan 2010 14:55:47 +0000 (UTC)	[thread overview]
Message-ID: <hhvjtj$quk$1@ger.gmane.org> (raw)
In-Reply-To: 1531E53627F1F749B4FE809BF2A4EB6701597BAD@WETMEX10.loepfe.com

On 2010-01-05, Vellemans, Noel <Noel.Vellemans@visionBMS.com> wrote:
> Re: at91sam9g20dfc_defconfig doesn't build (Grant Edwards)
>
>
>
> Please have a look at
> http://lists.busybox.net/pipermail/buildroot/2009-November/030376.html
>
> De-selecting 'at' will also solve the problem.

I don't have any need for 'at', so that works for me.

-- 
Grant Edwards                   grante             Yow! I feel partially
                                  at               hydrogenated!
                               visi.com            

      reply	other threads:[~2010-01-05 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11179.1262650413.28478.buildroot@busybox.net>
2010-01-05  7:17 ` [Buildroot] at91sam9g20dfc_defconfig doesn't build (Grant Edwards) Vellemans, Noel
2010-01-05 14:55   ` Grant Edwards [this message]

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='hhvjtj$quk$1@ger.gmane.org' \
    --to=grant.b.edwards@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