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] AVR32 defconfig
Date: Sat, 1 Sep 2007 18:27:51 +0200	[thread overview]
Message-ID: <20070901162750.GL11697@aon.at> (raw)
In-Reply-To: <1188456153.30555.4.camel@localhost.localdomain>

On Thu, Aug 30, 2007 at 08:42:33AM +0200, Hans-Christian Egtvedt wrote:
>On Wed, 2007-08-29 at 09:24 -0400, Jonathan Dumaresq wrote:
>
><cut Atmel snapshot of Buildroot>
 
>> i probably have setting in the config file that is not correct.
>
>Check what architecture is chosen in uClibc configuration:
>cd toolchain_build_avr32/uClibc-0.9.28.3
>make menuconfig

Generally you should not do this in order not to risk mis-configuration.
See docs/README

  parent reply	other threads:[~2007-09-01 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 13:24 [Buildroot] AVR32 defconfig Jonathan Dumaresq
2007-08-30  6:42 ` Hans-Christian Egtvedt
2007-08-31 18:55   ` Jonathan Dumaresq
2007-09-01 16:27   ` Bernhard Fischer [this message]
2007-09-04 13:00     ` Jonathan Dumaresq

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=20070901162750.GL11697@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