This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2, glibc-2.5)


That did the trick! Wonderful!

Should I report this as a bug to the arm gcc ports project? (And in that
case, would that project be the same as the "GCC ARM Improvement
Project" on http://www.inf.u-szeged.hu/gcc-arm/index.php?)

-- 
Arvid Brodin
Enea QiValue


-----Original Message-----
From: Lennert Buytenhek [mailto:buytenh@wantstofly.org] 
Sent: Tuesday, October 30, 2007 12:39 PM
To: Arvid Brodin
Cc: crossgcc@sourceware.org
Subject: Re: Non-working arm-unknown-linux-gnueabi toolchain (gcc-4.1.2,
glibc-2.5)

On Tue, Oct 30, 2007 at 12:33:51PM +0100, Arvid Brodin wrote:

> The CPU on my board is an Atmel at91rm9200, which use an arm920t core,

> which is an armv4t architecture, if I've understood correctly.

If you apply this patch and rebuild your toolchain, does it work?


Index: gcc/config/arm/linux-eabi.h
===================================================================
--- gcc/config/arm/linux-eabi.h
+++ gcc/config/arm/linux-eabi.h
@@ -45,7 +45,7 @@
    The ARM10TDMI core is the default for armv5t, so set
    SUBTARGET_CPU_DEFAULT to achieve this.  */  #undef
SUBTARGET_CPU_DEFAULT -#define SUBTARGET_CPU_DEFAULT
TARGET_CPU_arm10tdmi
+#define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm9tdmi
 
 #undef SUBTARGET_EXTRA_LINK_SPEC
 #define SUBTARGET_EXTRA_LINK_SPEC " -m armelf_linux_eabi"

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]