[ECOS] IMPORTANT ! for problem with GCC and INSIGHT build under CYGWIN !!!

[ECOS] IMPORTANT ! for problem with GCC and INSIGHT build under CYGWIN !!!

[Charles-Henri]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]

Hello,
 
for all users that want to build GCC and GDB under 
CYGWIN and an error occur with cygwin.dll version 1.1.1 or 1.1.2, 
I have a good news, I have found that is the 
"patch" command that transform output files in text mode with an \r in 
end
of line, then the command "tr -d '\r' 
ecos-gcc-2952.pat ¦ patch -p0" create output file that make problem with 
make
command.
 
I have build this little bash file for correct the 
files updated with path, you can apply the patch of gcc and gdb and
after go this little bash script file 
:
 
 
#!/bin/bash
# Correct the Patch error output in text mode with \r End 
of Line for GCC patch
cd /src/gcc/gcc-2.95.2
tr -d '\r' < gcc/Makefile.in > foo ; cp foo 
gcc/MakeFile.in
tr -d '\r' < gcc/configure.in > foo ; cp foo 
gcc/configure.in
tr -d '\r' < gcc/configure > foo ; cp foo 
gcc/configure
tr -d '\r' < gcc/reload1.c > foo ; cp foo 
gcc/reload1.c
tr -d '\r' < gcc/config/i386/i386elf.h > foo ; cp 
foo gcc/config/i386/i386elf.h
tr -d '\r' < gcc/config/i386/t-i386elf > foo ; cp 
foo gcc/config/i386/t-i386elf
tr -d '\r' < gcc/config/sparc/liteelf.h > foo ; cp 
foo gcc/config/sparc/liteelf.h
tr -d '\r' < gcc/config/sparc/sp86x-aout.h > foo ; 
cp foo gcc/config/sparc/sp86x-aout.h
tr -d '\r' < gcc/config/sparc/t-sp86x > foo ; cp foo 
gcc/config/sparc/t-sp86x
tr -d '\r' < gcc/config/sparc/sp86x-elf.h > foo ; cp 
foo gcc/config/sparc/sp86x-elf.h
tr -d '\r' < gcc/config/arm/arm.h > foo ; cp foo 
gcc/config/arm/arm.h
tr -d '\r' < gcc/config/arm/t-arm-elf > foo ; cp foo 
gcc/config/arm/t-arm-elf
tr -d '\r' < config.sub > foo ; cp foo 
config.sub
tr -d '\r' < gcc/config/mips/elf.h > foo ; cp foo 
gcc/config/mips/elf.h
tr -d '\r' < gcc/cstamp-h.in > foo ; cp foo 
gcc/cstamp-h.in
tr -d '\r' < gcc/config.in > foo ; cp foo 
gcc/config.in
rm foo
# Enf of Job
echo "End of Job !"
 
#!/bin/bash
# Correct the Patch error output in text mode with \r End 
of Line for Insight-5.0 patch
cd /src/gdb/insight-5.0
tr -d '\r' < tcl/generic/tclFileName.c > foo ; cp 
foo tcl/generic/tclFileName.c
tr -d '\r' < tcl/generic/tclInitScript.h > foo ; cp 
foo tcl/generic/tclInitScript.h
tr -d '\r' < tcl/win/tclWinFile.c > foo ; cp foo 
tcl/win/tclWinFile.c
rm foo
# Enf of Job
echo "End of Job !"
 
after apply this little script, you can build your tools with configure and 
make, all is right.
 
I have search for modify the patch command line (--binary)  or ... but 
unsuccessly, if any find how make more simply
 
like this :  patch -p0 < ecos-gcc-2952.pat ¦ tr -d 
'\r'     (this sample dosen't work unfortunately)
 
say me at charles-henri@prolectronic.com
 
 
 

Re: [ECOS] IMPORTANT ! for problem with GCC and INSIGHT build under CYGWIN !!!

[Jonathan Larmour]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

> Charles-Henri wrote:
> 
> Hello,
> 
> for all users that want to build GCC and GDB under CYGWIN and an error
> occur with cygwin.dll version 1.1.1 or 1.1.2,
> I have a good news, I have found that is the "patch" command that
> transform output files in text mode with an \r in end
> of line, then the command "tr -d '\r' ecos-gcc-2952.pat ¦ patch -p0"
> create output file that make problem with make
> command.

I have verified on my cygwin 1.1.2 system that there are no problems
applying patches. I even did a fresh reinstall just to be sure.

The only situation I can imagine could cause problems would be if you
applied the patch using a textmode mount point, but then built via a
binmode mount point. But I tried that too, and that works!

So are you sure there isn't some other problem with your setup? If you (or
other people - anyone?) are having genuine problems here, help me find out
what the difference is between your setup and mine.

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

[ECOS] NEC MIPS evlation board gcc build problem.

[Ling Su]

Hello,

After download the newest gcc and apply the patch, I have succeeded in
building the cross platform tool in Linux. Unfortunately even I used
cygwin1.1.2, I still meet problem in build the cross gcc compiler in Windows
NT.

Following is the log message I got, the process just hung there, I do not
know what is the reason...

make: Entering directory `/src/build/gcc'
make[1]: Entering directory `/src/build/gcc/libiberty'
make[2]: Entering directory `/src/build/gcc/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/src/build/gcc/libiberty/testsuite'
make[1]: Leaving directory `/src/build/gcc/libiberty'
make[1]: Entering directory `/src/build/gcc/texinfo'
make all-recursive
make[2]: Entering directory `/src/build/gcc/texinfo'
Making all in intl
make[3]: Entering directory `/src/build/gcc/texinfo/intl'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/src/build/gcc/texinfo/intl'
Making all in lib
make[3]: Entering directory `/src/build/gcc/texinfo/lib'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/src/build/gcc/texinfo/lib'
Making all in makeinfo
make[3]: Entering directory `/src/build/gcc/texinfo/makeinfo'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/src/build/gcc/texinfo/makeinfo'
Making all in util
make[3]: Entering directory `/src/build/gcc/texinfo/util'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/src/build/gcc/texinfo/util'
make[2]: Leaving directory `/src/build/gcc/texinfo'
make[1]: Leaving directory `/src/build/gcc/texinfo'
make[1]: Entering directory `/src/build/gcc/etc'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/src/build/gcc/etc'
make[1]: Entering directory `/src/build/gcc/gcc'
(cd intl && make all)
make[2]: Entering directory `/src/build/gcc/gcc/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/src/build/gcc/gcc/intl'
if [ -f libgcc.ready ] ; then \
 true; \
else \
 touch libgcc.ready; \
fi
make
GCC_FOR_TARGET="/src/build/gcc/gcc/xgcc -B/src/build/gcc/gcc/ -B/usr/local/c
ross/mips-elf/H-i686-pc-cygwin/mips64vr4300-elf/bin/ -I/usr/local/cross/mips
-elf/H-i686-pc-cygwin/mips64vr4300-elf/include" \
  HOST_PREFIX="" HOST_PREFIX_1="loser-" \
  AR_FOR_TARGET="mips64vr4300-elf-ar" \
  AR_CREATE_FOR_TARGET="mips64vr4300-elf-ar  rc" \
  AR_FLAGS_FOR_TARGET="" \
  OLDCC="cc" CCLIBFLAGS="-O" CFLAGS="-g -O2" \
  RANLIB_FOR_TARGET="mips64vr4300-elf-ranlib" \
  RANLIB_TEST_FOR_TARGET="[ -f mips64vr4300-elf-ranlib ] ||
[ "i686-pc-cygwin" = "mips64vr4300-unknown-elf" ] && [ -f
/usr/bin/ranlib -o -f /bin/ranlib ] )" \
  LIBGCC2_CFLAGS="-O2  -DCROSS_COMPILE -DIN_GCC    `echo -g -O2|sed -e
's/-pedantic//g' -e 's/-Wtraditional//g'` -isystem ./include  -G
 -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc" \


INCLUDES="-I. -I/src/gcc/egcs-20000530/gcc -I/src/gcc/egcs-20000530/gcc/conf
ig -I/src/gcc/egcs-20000530/gcc/../include" MAYBE_USE_COLLECT2="" \
  CONFIG_H="" MACHMODE_H="machmode.h machmode.def" \
  LIB1ASMSRC='' \
  -f libgcc.mk all
make[2]: Entering directory `/src/build/gcc/gcc'
/src/build/gcc/gcc/xgcc -B/src/build/gcc/gcc/ -B/usr/local/cross/mips-elf/H-
i686-pc-cygwin/mips64vr4300-elf/bin/ -I/usr/local/cross/mips-elf/H-i686-pc-c
ygwin/mips64vr4300-elf/include -O2  -DCROSS_COMPILE -DIN_GCC    -g -O2 -isys
tem ./include  -G
0 -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I/src/gcc/e
gcs-20000530/gcc -I/src/gcc/egcs-20000530/gcc/config -I/src/gcc/egcs-2000053
0/gcc/../include  -DL_muldi3 -c /src/gcc/egcs-20000530/gcc/libgcc2.c -o
libgcc/./_muldi3.o

Hopefully somebody could kindly help me out of this.

Thanks!

Best Regards,
-Ling

[ECOS] Re: NEC MIPS evlation board gcc build problem.

[Jonathan Larmour]

Ling Su wrote:
> 
> Hello,
> 
> After download the newest gcc and apply the patch, I have succeeded in
> building the cross platform tool in Linux. Unfortunately even I used
> cygwin1.1.2, I still meet problem in build the cross gcc compiler in Windows
> NT.
> 
> Following is the log message I got, the process just hung there, I do not
> know what is the reason...
> [snip]
> Hopefully somebody could kindly help me out of this.

It would be best to take this problem to the gcc mailing list. See
http://gcc.gnu.org/ and in particular http://gcc.gnu.org/lists.html

You should tell them that this target is effectively the same as
mips64-elf. Emphasise that it works in Linux.

Good luck,

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