From: Andrew Lunn <andrew@lunn.ch>
To: Aniket S Joshi <aniketsj@myw.ltindia.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Error while compiling Jffs2 package
Date: Mon, 24 May 2004 23:29:00 -0000 [thread overview]
Message-ID: <20040524133140.GG32174@lunn.ch> (raw)
In-Reply-To: <s0b23e4b.010@EMAIL>
On Mon, May 24, 2004 at 06:26:11PM +0530, Aniket S Joshi wrote:
> Hi All,
> I'm trying to build eCos for the Hitachi Sh-7729 board and everything worked
> fine until I added the jffs2 package. Make now reports an error, but the
> compiler only reports warnings and no output file is created by the
> compiler.
> I'm using the latest version of eCos
> The output is shown below
>
> sh-elf-gcc -c -I/ecos-c/ecos-work/test20_install/include
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/fs/jffs2/v2_0
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/fs/jffs2/v2_0/src
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/fs/jffs2/v2_0/tests
-I. -I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/fs/jffs2/v2_0/src/ -ml
-m3 -Wall -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual
-ggdb -O2 -ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -D__ECOS -nostdinc
-iwithprefix include -Werror -Wp,-MD,src/fs-ecos.tmp -o
^^^^^^^^
This causes gcc to turn all warnings into errors. So make it stopping.
You are using an old copy of the sources. This flag was removed at the
beginning of december last year. Is suggest you update your sources.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-05-24 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 13:25 Aniket S Joshi
2004-05-24 23:29 ` Andrew Lunn [this message]
2004-05-28 13:51 Aniket S Joshi
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=20040524133140.GG32174@lunn.ch \
--to=andrew@lunn.ch \
--cc=aniketsj@myw.ltindia.com \
--cc=ecos-discuss@sources.redhat.com \
/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).