Re: [ECOS] Building eCOS for the first time (or hoping so)

Re: [ECOS] Building eCOS for the first time (or hoping so)

[Jonathan Larmour]

Mathieu Routhier wrote:
> 
> >mount -f -t c:/ /c
> 
> It has already been done !  Yeah, that text mode mount got me some other
> errors but I'm now rid of them.
> 
> No, my paths are ok.  It is just that there is a very strange error
> message with the assembler.  There seem to be an error in the process of
> compiling a c file.  The assembler gets called in the end and the file
> that is passed in parameter does not have a valid name.  Or something
> like that....
> 
> Anyone experienced that ?

I wonder if it's something to do with /tmp. You could try mounting /tmp in
text mode as well just to see.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

RE: [ECOS] Building eCOS for the first time (or hoping so)

[Mathieu Routhier]

-----Original Message-----
From: jlarmour@cambridge.redhat.com
[ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
Sent: Tuesday, September 18, 2001 6:46 PM
To: Mathieu Routhier; eCos discussion
Subject: Re: [ECOS] Building eCOS for the first time (or hoping so)

Mathieu Routhier wrote:
> 
> >mount -f -t c:/ /c
> 
> It has already been done !  Yeah, that text mode mount got me some
other
> errors but I'm now rid of them.
> 
> No, my paths are ok.  It is just that there is a very strange error
> message with the assembler.  There seem to be an error in the process
of
> compiling a c file.  The assembler gets called in the end and the file
> that is passed in parameter does not have a valid name.  Or something
> like that....
> 
> Anyone experienced that ?

I wonder if it's something to do with /tmp. You could try mounting /tmp
in
text mode as well just to see.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062
Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine

Re: [ECOS] Building eCOS for the first time (or hoping so)

[Grant Edwards]

On Tue, Sep 18, 2001 at 11:07:15PM +0100, Jonathan Larmour wrote:
> Mathieu Routhier wrote:
>
> > Anyway, now the project fails during compilation.  I've made no
> > modification to the default config.  At the bottom of the message is the
> > line that generates the error.  The part following 'Assembler messages'
> > reads 'for reading.open' but is really 'Could not open [] for reading',
> > where [] is a 0x0D ascii character.
> > 
> > So the Assembler tries to open the file called 0x0D.  This is bad :)
> 
> You have to play with the cygwin mount points. Make sure the eCos sources
> are mounted in "text" mode, e.g. with:
> 
> mount -f -t c:/ /c

And remember to use an editor that preserves Unix line endings
in source files.

We're in the initial stages of shipping an eCos development kit
for our platform.  It includes bot Cygwin and Linux toolchains,
examples apps, etc.  I'm convinced that you're better off in
the long run if you do eCos development under Linux -- even if
you have to spend a couple weeks getting used to Linux.

-- 
Grant Edwards
grante@visi.com

Re: [ECOS] Building eCOS for the first time (or hoping so)

[Jonathan Larmour]

Mathieu Routhier wrote:
> 
> Hi guys,
> 
> I'm new to eCOS and I'm still trying to build my first eCOS binary.
> I've had a lot of trouble getting the arm-elf-gcc to work.  First the
> eCOS config tool generated makefiles with corrupted paths (like putting
> double slashes at the beginning of my path).  I had to modify the
> makefiles by hand.  What have I done wrong?
> 
> Anyway, now the project fails during compilation.  I've made no
> modification to the default config.  At the bottom of the message is the
> line that generates the error.  The part following 'Assembler messages'
> reads 'for reading.open' but is really 'Could not open [] for reading',
> where [] is a 0x0D ascii character.
> 
> So the Assembler tries to open the file called 0x0D.  This is bad :)
> 
> What I'm I to do?  What does this problem means?  Is there hope at all?

You have to play with the cygwin mount points. Make sure the eCos sources
are mounted in "text" mode, e.g. with:

mount -f -t c:/ /c

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

[ECOS] Building eCOS for the first time (or hoping so)

[Mathieu Routhier]

Hi guys,

I'm new to eCOS and I'm still trying to build my first eCOS binary.
I've had a lot of trouble getting the arm-elf-gcc to work.  First the
eCOS config tool generated makefiles with corrupted paths (like putting
double slashes at the beginning of my path).  I had to modify the
makefiles by hand.  What have I done wrong?

Anyway, now the project fails during compilation.  I've made no
modification to the default config.  At the bottom of the message is the
line that generates the error.  The part following 'Assembler messages'
reads 'for reading.open' but is really 'Could not open [] for reading',
where [] is a 0x0D ascii character.

So the Assembler tries to open the file called 0x0D.  This is bad :)

What I'm I to do?  What does this problem means?  Is there hope at all?

Mathieu Routhier


----------------------
arm-elf-gcc -c  -I/c/DEV/SecBuild/Untitled_install/include
-I/c/eCos/packages/ha
l/arm/arch/v1_3_1 -I/c/eCos/packages/hal/arm/arch/v1_3_1/src
-I/c/eCos/packages/
hal/arm/arch/v1_3_1/tests -I.
-I/c/eCos/packages/hal/arm/arch/v1_3_1/src/ -mcpu=
arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded
-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -f
vtable-gc -finit-priority -Wp,-MD,src/hal_misc.tmp -o
src/hal_arm_arch_hal_misc.
o /c/eCos/packages/hal/arm/arch/v1_3_1/src/hal_misc.c
Assembler messages:
 for reading.open
: No such file or directory
make[1]: *** [src/hal_misc.o.d] Error 1