public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: C B <csb_80@hotmail.com>
To: Lars Poeschel <larsi@wh2.tu-dresden.de>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] eCos compatible with arm-elf-gcc version 4.1.1?
Date: Thu, 22 Nov 2007 16:42:00 -0000	[thread overview]
Message-ID: <BAY105-W9CE74D51C0F1EACC05509EA790@phx.gbl> (raw)
In-Reply-To: <DBEE2411-0F53-4AE4-8DE7-9E194ECC09CA@wh2.tu-dresden.de>


Sorry about mixing up the threads.
 
My configuration works perfectly with gcc 3.2.1.  No problems finding any files or building eCos.  The ONLY thing that I changed was to point the build tools at the 4.1.1 version of gcc and suddenly it can't find files that are in fact there.  Seems like a problem related to gcc 4.1.1 in some way.




> CC: ecos-discuss@ecos.sourceware.org
> From: larsi@wh2.tu-dresden.de
> Subject: Re: [ECOS] eCos compatible with arm-elf-gcc version 4.1.1?
> Date: Thu, 22 Nov 2007 15:05:12 +0100
> To: csb_80@hotmail.com
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> I am successfully able to build the latest eCos from CVS using
>> arm-elf-gcc version 3.2.1 that I got from eCosCentric. In order to
>> take advantage of some additional instructions for my target I was
>> attempting to update to arm-elf-gcc version 4.1.1 but I'm not able
>> to build eCos now. I'm using the configtool in Windows XP and the
>> only change is that I'm pointing to a new set of build tools. The
>> error I'm getting looks like this:
>>
>>
>> ...
>> headers finished
>> make -r -C hal/arm/arch/current arm.inc
>> make[1]: Entering directory `/ecos-c/cygwin/opt/ecos/ecos-cvs/tmp3/
>> test_build/hal/arm/arch/current'
>> arm-elf-gcc.exe: /opt/ecos/ecos-cvs/ecos/packages/hal/arm/arch/
>> current/src/hal_mk_defs.c: No such file or directory
>
> As you can see here, the compiler is not able to find a source file.
> This is not a problem of gcc, but of your configuration.
> Check your ECOS_REPOSITORY shell variable,
> check that you set up your build environment with this variable,
> and finally check that all source files are in place, propably you
> have to update your local cvs tree.
>
>> arm-elf-gcc -finline-limit=7000 -mcpu=arm9tdmi -Wall -Wpointer-
>> arith -Wstrict-prototypes -Winline -Wundef -g -O2 -ffunction-
>> sections -fdata-sections -fno-exceptions -I/ecos-c/cygwin/opt/
>> ecos/ecos-cvs/tmp3/test_install/include -I/opt/ecos/ecos-cvs/ecos/
>> packages/hal/arm/arch/current -I/opt/ecos/ecos-cvs/ecos/packages/
>> hal/arm/arch/current/src -I/opt/ecos/ecos-cvs/ecos/packages/hal/arm/
>> arch/current/tests -I. -Wp,-MD,arm.tmp -o hal_mk_defs.tmp -S /opt/
>> ecos/ecos-cvs/ecos/packages/hal/arm/arch/current/src/hal_mk_defs.c
>> arm-elf-gcc.exe: no input files
>
> Here you can see again, that the source file was not found.
>
>> make[1]: Leaving directory `/ecos-c/cygwin/opt/ecos/ecos-cvs/tmp3/
>> test_build/hal/arm/arch/current'
>> make[1]: *** [arm.inc] Error 1
>> make: Leaving directory `/ecos-c/cygwin/opt/ecos/ecos-cvs/tmp3/
>> test_build'
>> make: *** [build] Error 2
>>
>>
>> Is gcc 4.x not supported or am I missing something else? If not,
>> is 3.2.1 (which is fairly old) that latest?
>
> Generally ecos should build for gcc4.x.
>
> Lars
>
> P.S.: Next time, don't answer to a previous mail, if you start a new
> thread!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (Darwin)
>
> iD8DBQFHRYyb3m3cZ1XsbwcRAkZmAJ9rVreAajPn5/AaEMgSZjYEfuzMJgCeOTqZ
> rz2HBEmZ4HsllpSaAEGsACk=
> =wTd1
> -----END PGP SIGNATURE-----

_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/connect.html?ocid=TXT_TAGLM_Wave2_newways_112007

--
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:[~2007-11-22 15:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 18:54 [ECOS] networking support for my eCos application C B
2007-11-02 19:08 ` Gary Thomas
2007-11-05 16:12   ` C B
2007-11-05 18:43     ` Andrew Lunn
     [not found]       ` <BAY105-W2585C1EB05E16C54EA73C5EA890@phx.gbl>
2007-11-06  8:34         ` Andrew Lunn
2007-11-08 20:01   ` C B
2007-11-08 21:05     ` Andrew Lunn
2007-11-09  9:22     ` [ECOS] " John Dallaway
2007-11-09 13:32       ` [ECOS] " C B
2007-11-09 18:48         ` C B
2007-11-09 18:55           ` Andrew Lunn
2007-11-12 11:52             ` C B
2007-11-12 12:27               ` Gary Thomas
2007-11-12 18:11                 ` C B
2007-11-14 13:30                   ` [ECOS] Adding xscale support to my eCos config C B
2007-11-14 14:05                     ` Andrew Lunn
2007-11-14 14:13                       ` Mark Salter
2007-11-14 15:23                       ` C B
2007-11-14 15:24                         ` Gary Thomas
2007-11-14 20:11                           ` C B
2007-11-14 20:42                             ` C B
2007-11-16 18:15                               ` [ECOS] Performance timing C B
2007-11-16 19:47                                 ` Gary Thomas
2007-11-16 19:55                                   ` C B
2007-11-17  7:07                                     ` Mike Arthur
2007-11-19  5:19                                       ` C B
2007-11-19 14:36                                         ` Gary Thomas
2007-11-22 13:39                                           ` [ECOS] eCos compatible with arm-elf-gcc version 4.1.1? C B
2007-11-22 14:28                                             ` Lars Poeschel
2007-11-22 16:42                                               ` C B [this message]
2007-11-27 14:38                                               ` C B
2007-11-28 13:24                                                 ` C B
     [not found]             ` <BAY105-W28BEA5A1C91693C8BE5C8FEA870@phx.gbl>
2007-11-12 12:07               ` [ECOS] RE: networking support for my eCos application Andrew Lunn
2007-11-12 18:05                 ` C B

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=BAY105-W9CE74D51C0F1EACC05509EA790@phx.gbl \
    --to=csb_80@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=larsi@wh2.tu-dresden.de \
    /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).