From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] sysroot not anabled even when BR2_GCC_VERSION_4_2_1 is selected
Date: Thu, 20 Sep 2007 01:28:04 -0700 (PDT) [thread overview]
Message-ID: <12792950.post@talk.nabble.com> (raw)
Hi All,
I just tried latest buildroot snapshot and below is my buildroot config.
What i observed is that BR2_TOOLCHAIN_SYSROOT i snot selected even though i
have enabled gcc 4.2.1. Let me know if any one has a quickest solution. LEt
me know if anyone needs more info.
Regards
Gururaja
BR2_arm=y
BR2_arm926t=y
BR2_ARM_TYPE="ARM926T"
BR2_ARM_EABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="arm9tdmi"
BR2_PREFER_STATIC_LIB=y
#
#
# Toolchain type
#
BR2_TOOLCHAIN_BUILDROOT=y
# BR2_TOOLCHAIN_EXTERNAL is not set
BR2_TOOLCHAIN_NORMAL=y
# BR2_TOOLCHAIN_ATMEL_AVR32 is not set
#
# Gcc Options
#
# BR2_GCC_VERSION_3_3_5 is not set
# BR2_GCC_VERSION_3_3_6 is not set
# BR2_GCC_VERSION_3_4_2 is not set
# BR2_GCC_VERSION_3_4_3 is not set
# BR2_GCC_VERSION_3_4_4 is not set
# BR2_GCC_VERSION_3_4_5 is not set
# BR2_GCC_VERSION_3_4_6 is not set
# BR2_GCC_VERSION_4_0_0 is not set
# BR2_GCC_VERSION_4_0_1 is not set
# BR2_GCC_VERSION_4_0_2 is not set
# BR2_GCC_VERSION_4_0_3 is not set
# BR2_GCC_VERSION_4_0_4 is not set
# BR2_GCC_VERSION_4_1_0 is not set
# BR2_GCC_VERSION_4_1_1 is not set
# BR2_GCC_VERSION_4_1_2 is not set
# BR2_GCC_VERSION_4_2_0 is not set
BR2_GCC_VERSION_4_2_1=y
# BR2_GCC_IS_SNAP is not set
BR2_GCC_VERSION="4.2.1"
# BR2_GCC_USE_SJLJ_EXCEPTIONS is not set
--
View this message in context: http://www.nabble.com/sysroot-not-anabled-even-when-BR2_GCC_VERSION_4_2_1-is-selected-tf4486096.html#a12792950
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2007-09-20 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 8:28 Hebbar [this message]
2007-09-20 9:11 ` [Buildroot] sysroot not anabled even when BR2_GCC_VERSION_4_2_1 is selected Bernhard Fischer
2007-09-20 9:29 ` Bernhard Fischer
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=12792950.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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