From: "Andy Jackson" <andy@grapevinetech.co.uk>
To: <Emmanuel.Viollet@webdyn.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: AW: [ECOS] Ecosconfig and configtool
Date: Wed, 10 May 2006 09:12:00 -0000 [thread overview]
Message-ID: <001d01c67411$e7b59160$9701a8c0@Kimbara> (raw)
In-Reply-To: <4461A8DA.5020803@webdyn.com>
Try just removing '-mno-short-load-words' from the entry for 'Global
compiler flags' in the 'Global build options' folder.
I think more recent versions of GCC refuse to accept this option any more.
Andy..
----- Original Message -----
From: "Emmanuel Viollet" <Emmanuel.Viollet@webdyn.com>
To: "Ram Sudhir Tadavarthi" <ram.tadavarthi@netco.de>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Wednesday, May 10, 2006 9:48 AM
Subject: Re: AW: [ECOS] Ecosconfig and configtool
> Hi.
>
> Thanks.
> Actually my current problem is that if I use configtool, I get the
> following error upon compilation :
> arm-elf-gcc -finline-limit=7000 -mcpu=arm7tdmi -mno-short-load-words -Wall
> -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual
> -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -I/ecos-e/Projets/eCOS/Tests/OlimexLPC2106PPP/ecos_install/include
> -I/opt/ecos/ecos/packages/hal/arm/arch/current -I/opt/ecos/ecos/packages/hal/arm/arch/current/src
> -I/opt/ecos/ecos/packages/hal/arm/arch/current/tests -I. -Wp,-MD,arm.tmp
> -o hal_mk_defs.tmp -S
> /opt/ecos/ecos/packages/hal/arm/arch/current/src/hal_mk_defs.c
> make[1]: Leaving directory
> `/ecos-e/Projets/eCOS/Tests/OlimexLPC2106PPP/ecos_build/hal/arm/arch/current'
> cc1: error: invalid option `no-short-load-words'
> make: Leaving directory
> `/ecos-e/Projets/eCOS/Tests/OlimexLPC2106PPP/ecos_build'
> cc1: warning: command line option "-Woverloaded-virtual" is valid for
> C++/ObjC++ but not for C
> cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but
> not for C
> make[1]: *** [arm.inc] Error 1
> make: *** [build] Error 2
>
> whereas if I compile using make in the cygwin shell, it works.
> Apparently configtool isn't using the correct cc1 compiler. Where can I
> configure this?
>
> In advance, thanks.
>
>
> Ram Sudhir Tadavarthi a écrit :
>> Hi,
>>
>> Configtool is Graphical tool and ecosconfig is command line tool. You can
>> use either as per your convenience. I prefer to use configtool. IMHO both
>> should provide same results though I never tried to use ecosconfig tool
>> much.
>>
>> Warm regards,
>> ram
>>
>> -----Ursprüngliche Nachricht-----
>> Von: ecos-discuss-owner@ecos.sourceware.org
>> [mailto:ecos-discuss-owner@ecos.sourceware.org] Im Auftrag von Emmanuel
>> Viollet
>> Gesendet: Mittwoch, 10. Mai 2006 10:25
>> An: ecos-discuss@ecos.sourceware.org
>> Betreff: [ECOS] Ecosconfig and configtool
>>
>> Hi.
>>
>> Under Windows, which tool am I supposed to use? ecosconfig or configtool?
>> I see that the two tools do not produce the same results (different
>> directory structures for instance).
>> Is this normal?
>>
>> In advance, thanks.
>>
>>
>
>
> --
> Emmanuel Viollet
> Software engineer
> Webdyn
> e-mail : Emmanuel.Viollet@webdyn.com
> Tel : +33 (0)1 39 04 29 55
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
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:[~2006-05-10 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 8:25 Emmanuel Viollet
2006-05-10 8:34 ` Andrew Lunn
2006-05-10 8:37 ` AW: " Ram Sudhir Tadavarthi
2006-05-10 8:48 ` Emmanuel Viollet
2006-05-10 9:12 ` Andy Jackson [this message]
2006-05-10 10:19 ` Emmanuel Viollet
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='001d01c67411$e7b59160$9701a8c0@Kimbara' \
--to=andy@grapevinetech.co.uk \
--cc=Emmanuel.Viollet@webdyn.com \
--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).