[ECOS] Problems making gcc

[ECOS] Problems making gcc

[jens.ohlund]

My problem is that even if i follow the given instructoins it crashes...

I run NT4 and i want to install ecos 1.3.1 with insight for the ARM. (AEB-1).

When following the instructions on the homepage I first installed cygwin, no problems.
Then installed ecos, no problem.
Mounted c: and d:, no rpoblem.
Unpacking everything, no problem.
Patching gcc and insight with given methof (tr -d ...), no problem
Configuring and building binutils, no problem
Configuring gcc, ok i think.
Building gcc, crash.

This is what happened when it starts crashing:
gcc -DCROSS_COMPILE -DIN_GCC     -g -O2  -DHAVE_CONFIG_H    -I. -I/src/gcc/gcc-2.95.2/gcc -I/src/gcc/gcc-2.95.2/gcc/config -I/src/gcc/gcc-2.95.2/gcc/../include \
  -DGCC_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/include\" \
  -DGPLUSPLUS_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../..`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/[^/]*|/..|g'`/include/g++-3\" \
  -DLOCAL_INCLUDE_DIR=\"/tools/include\" \
  -DCROSS_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/$||' -e 's|^[^/]|/|' -e 's|/[^/]*|../|g'`arm-elf/sys-include\" \
  -DTOOL_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/$||' -e 's|^[^/]|/|' -e 's|/[^/]*|../|g'`arm-elf/include\" \
  -c `echo /src/gcc/gcc-2.95.2/gcc/cccp.c | sed 's,^\./,,'`
In file included from /src/gcc/gcc-2.95.2/gcc/config/arm/aout.h:301,
                 from /src/gcc/gcc-2.95.2/gcc/config/arm/elf.h:354,
                 from /src/gcc/gcc-2.95.2/gcc/config/arm/unknown-elf.h:171,
                 from tm.h:6,
                 from /src/gcc/gcc-2.95.2/gcc/config/i386/xm-i386.h:43,
                 from config.h:8,
                 from /src/gcc/gcc-2.95.2/gcc/cccp.c:21:
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: parse error before `{'
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: warning: unknown escape sequence: `\' followed by char code 0xd
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:227: warning: unknown escape sequence: `\' followed by char code 0xd
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:228: warning: unknown escape sequence: `\' followed by char code 0xd

And it continues like that ALOT.

I have used binutils-20000608, gcc 2.95.2. Installed cygwin 1.1.2. And tried lots more. Searched for it in the archives. Seen some
ideas but none worked. Now i've tried to install this for 3 days and I'm desperate. ANYbody got an idea ?

Yours, soon-to-be-hairless
Jens Ohlund

Re: [ECOS] Problems making gcc

[Hugo 'NOx' Tyson]

jens.ohlund@secrc.abb.se writes:
> My problem is that even if i follow the given instructoins it crashes...
> 
> I run NT4 and i want to install ecos 1.3.1 with insight for the ARM. (AEB-1).

> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: parse error before `{'
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: warning: unknown escape sequence: `\' followed by char code 0xd
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:227: warning: unknown escape sequence: `\' followed by char code 0xd
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:228: warning: unknown escape sequence: `\' followed by char code 0xd
> 
> And it continues like that ALOT.

I don't know a fix (not being an NT user) but the cause is line endings.

The compiler expects '\' '<newline>' to do continuation lines, but it is
seeing  '\' '<return>' '<newline>'.

Therefore a) warning about unknown escape sequence, and b) much worse,
continuation lines in macro definitions do not work at all, so it all goes
horribly wrong.

Mount modes, binary vs. text?

Or down to not setting "binary" in ftp when you acquired/copied/moved the
original sources?  (though that usually snafus up a compressed archive lots
worse)

ISTR talking to our man Al, whom I have copied this msg, about a similar
thing yesterday.  Al, can you shed any light on this?

	- Huge

RE: [ECOS] Problems making gcc

[Alex Schuilenburg]

> ISTR talking to our man Al, whom I have copied this msg, about a similar
> thing yesterday.  Al, can you shed any light on this?

Yes.  Switch to the latest cygwin1.dll (1.1.2) released on Wednesday.  See
  http://sourceware.cygnus.com/ml/cygwin-announce/2000/msg00023.html
for details on the fixes and
  http://sourceware.cygnus.com/cygwin/mirrors.html
on where to download.

I managed to get around the problem initially by having the build directory
mounted in text mode.

These are cygwin issues BTW (my problem was with a totally different set of
sources), not eCos, and have already been addressed on
cygwin@sourceware.cygnus.com (archives available at
http://sourceware.cygnus.com/ml/cygwin/ ).

HTH
-- Alex

Re: [ECOS] Problems making gcc

[Jonathan Larmour]

Alex Schuilenburg wrote:
> 
> > ISTR talking to our man Al, whom I have copied this msg, about a similar
> > thing yesterday.  Al, can you shed any light on this?
> 
> Yes.  Switch to the latest cygwin1.dll (1.1.2) released on Wednesday.  See
>   http://sourceware.cygnus.com/ml/cygwin-announce/2000/msg00023.html
> for details on the fixes and
>   http://sourceware.cygnus.com/cygwin/mirrors.html
> on where to download.

Jens already said he was using 1.1.2, but read on.
 
> I managed to get around the problem initially by having the build directory
> mounted in text mode.

I'm somewhat sceptical that's the fix since the problem is on the drive
containing the sources, not the build tree.

No, my guess is that Jens installed the eCos patches to gcc 2.95.2 (which
include a patch to arm.h) when using cygwin 1.1.1, and then found this
problem and *then* updated to cygwin 1.1.2. By that point it was too late -
arm.h already had got CRs put in it.

So instead, now that Jens is using 1.1.2, he should unpack the original
tarball again and reapply the patches. All should then be happy.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] Problems making gcc

[Hugo 'NOx' Tyson]

jens.ohlund@secrc.abb.se writes:
> My problem is that even if i follow the given instructoins it crashes...
> 
> I run NT4 and i want to install ecos 1.3.1 with insight for the ARM. (AEB-1).

> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: parse error before `{'
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: warning: unknown escape sequence: `\' followed by char code 0xd
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:227: warning: unknown escape sequence: `\' followed by char code 0xd
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:228: warning: unknown escape sequence: `\' followed by char code 0xd
> 
> And it continues like that ALOT.

I don't know a fix (not being an NT user) but the cause is line endings.

The compiler expects '\' '<newline>' to do continuation lines, but it is
seeing  '\' '<return>' '<newline>'.

Therefore a) warning about unknown escape sequence, and b) much worse,
continuation lines in macro definitions do not work at all, so it all goes
horribly wrong.

Mount modes, binary vs. text?

Or down to not setting "binary" in ftp when you acquired/copied/moved the
original sources?  (though that usually snafus up a compressed archive lots
worse)

ISTR talking to our man Al, whom I have copied this msg, about a similar
thing yesterday.  Al, can you shed any light on this?

	- Huge