public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Doyle, Patrick" <WPD@dtccom.com>
To: "'Andrew Lunn'" <andrew@lunn.ch>, "Doyle, Patrick" <WPD@dtccom.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] JFFS2 on ARM target
Date: Thu, 09 Mar 2006 16:18:00 -0000	[thread overview]
Message-ID: <3EDBCCE80E95E744A99895CA464987C4A7D293@dtcsrvr09> (raw)

> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch] 
> Sent: Wednesday, March 08, 2006 4:58 PM
> To: Doyle, Patrick
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] JFFS2 on ARM target
> 
> packages/fs/jffs2/current/src/fs-ecos.c:24
> 
> #if (__GNUC__ == 3) && (__GNUC_MINOR__ == 2) && defined 
> (__ARM_ARCH_4__)
> #error This compiler is known to be broken. Please see:
> #error 
> http://ecos.sourceware.org/ml/ecos-patches/2003-08/msg00006.html
> #endif
> 
> 2003-09-23  Andrew Lunn  <andrew.lunn@ascom.ch>
> 
>         * src/fs-ecos.c: Added test to detect known broken 
> ARM compiler
> 
>         Andrew
> 
Thanks Andrew,
I'll look at mtd distribution, see if it includes Øyvind's patch, and figure
out what to do next based on what I find there.  In the mean time,
experimental evidence suggests that the 'defined(__ARM_ARCH_4__)' should be
'defined(__ARM_ARCH_4T_)' in fs-ecos.c.  At least on my system, which
compiles fs-ecos.c with the following command:

arm-elf-gcc -c  -I/home/wpd/ess/redboot/dbw-redboot-ram/install/include
-I/home/wpd/eCos/ecos-20060228/packages/fs/jffs2/current
-I/home/wpd/eCos/ecos-20060228/packages/fs/jffs2/current/src
-I/home/wpd/eCos/ecos-20060228/packages/fs/jffs2/current/tests -I.
-I/home/wpd/eCos/ecos-20060228/packages/fs/jffs2/current/src/
-finline-limit=7000 -mcpu=arm9 -Wall -Wpointer-arith -Wstrict-prototypes
-Winline -Wundef  -g -O2 -ffunction-sections -fdata-sections
-fno-exceptions   -D__ECOS -nostdinc -iwithprefix include
-Wp,-MD,src/fs-ecos.tmp -o src/fs_jffs2_fs-ecos.o
/home/wpd/eCos/ecos-20060228/packages/fs/jffs2/current/src/fs-ecos.c

--wpd

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-03-09 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 16:18 Doyle, Patrick [this message]
2006-03-09 20:42 ` Andrew Lunn
2006-06-20 14:35   ` Jürgen Lambrecht
  -- strict thread matches above, loose matches on Subject: below --
2006-03-09 20:11 Doyle, Patrick
2006-03-09 20:39 ` Andrew Lunn
2006-03-08 20:00 Doyle, Patrick
2006-03-08 21:58 ` Andrew Lunn
2006-03-08 23:03   ` Newsgroups Reader

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=3EDBCCE80E95E744A99895CA464987C4A7D293@dtcsrvr09 \
    --to=wpd@dtccom.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).