Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel
Date: Wed, 26 Sep 2007 17:15:49 -0700 (PDT)	[thread overview]
Message-ID: <20070927001549.89148A5E23@busybox.net> (raw)

Author: ulf
Date: 2007-09-26 17:15:46 -0700 (Wed, 26 Sep 2007)
New Revision: 20051

Log:
Update AVR32 config to avoid questions during uclibc make oldconfig

Modified:
   trunk/buildroot/target/device/Atmel/uClibc.config.avr32


Changeset:
Modified: trunk/buildroot/target/device/Atmel/uClibc.config.avr32
===================================================================
--- trunk/buildroot/target/device/Atmel/uClibc.config.avr32	2007-09-26 23:21:43 UTC (rev 20050)
+++ trunk/buildroot/target/device/Atmel/uClibc.config.avr32	2007-09-27 00:15:46 UTC (rev 20051)
@@ -37,10 +37,11 @@
 # ARCH_HAS_NO_MMU is not set
 ARCH_HAS_MMU=y
 UCLIBC_HAS_FLOATS=y
+# UCLIBC_HAS_FPU is not set
 # HAS_FPU is not set
 UCLIBC_HAS_SOFT_FLOAT=y
 DO_C99_MATH=y
-KERNEL_SOURCE="/home/avr32/buildroot/toolchain_build_avr32/linux"
+KERNEL_SOURCE="/home/ulf/projects/Buildroot/20070927/buildroot/toolchain_build_avr32/linux"
 C_SYMBOL_PREFIX=""
 HAVE_DOT_CONFIG=y
 
@@ -101,7 +102,6 @@
 # UCLIBC_HAS_LOCALE is not set
 UCLIBC_HAS_HEXADECIMAL_FLOATS=y
 UCLIBC_HAS_GLIBC_CUSTOM_PRINTF=y
-# USE_OLD_VFPRINTF is not set
 UCLIBC_PRINTF_SCANF_POSITIONAL_ARGS=9
 UCLIBC_HAS_SCANF_GLIBC_A_FLAG=y
 # UCLIBC_HAS_STDIO_BUFSIZ_NONE is not set
@@ -141,7 +141,7 @@
 #
 SHARED_LIB_LOADER_PREFIX="/lib"
 RUNTIME_PREFIX="/"
-DEVEL_PREFIX="/usr"
+DEVEL_PREFIX="/usr/"
 
 #
 # uClibc security related options
@@ -151,7 +151,7 @@
 #
 # uClibc development/debugging options
 #
-CROSS_COMPILER_PREFIX="/home/avr32/buildroot/build_avr32/staging_dir/bin/avr32-linux-uclibc-"
+CROSS_COMPILER_PREFIX="/home/ulf/projects/Buildroot/20070927/buildroot/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-"
 # DODEBUG is not set
 # DODEBUG_PT is not set
 # DOASSERTS is not set

             reply	other threads:[~2007-09-27  0:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  0:15 ulf at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-29 21:29 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel ulf at uclibc.org
2009-01-11 21:15 ulf at uclibc.org
2008-12-20 22:26 ulf at uclibc.org
2008-12-20 22:23 ulf at uclibc.org
2008-12-20 22:17 ulf at uclibc.org
2008-12-23  9:42 ` Peter Korsgaard
2008-03-30 22:23 ulf at uclibc.org
2008-03-29 20:38 ulf at uclibc.org
2008-01-08 21:03 ulf at uclibc.org
2007-10-18 12:37 ulf at uclibc.org
2007-10-12 15:18 ulf at uclibc.org
2007-10-12 15:17 ulf at uclibc.org
2007-09-28 22:20 aldot at uclibc.org
2007-09-04 16:21 ulf at uclibc.org
2007-08-22 21:47 ulf at uclibc.org
2007-08-19 23:13 ulf at uclibc.org
2007-08-20 16:05 ` Bernhard Fischer
2007-08-01 11:53 ulf at uclibc.org
2007-07-29  8:33 ulf at uclibc.org
2007-07-29  7:32 ulf at uclibc.org
2007-07-29  7:22 ulf at uclibc.org
2007-07-29  7:19 ulf at uclibc.org
2007-07-20 11:03 ulf at uclibc.org
2007-06-07 10:48 aldot at uclibc.org

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=20070927001549.89148A5E23@busybox.net \
    --to=ulf@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