[ECOS] Rebuild gcc-4.0.0 with newlib-1.13.0 for mipsisa32-elf

[ECOS] Rebuild gcc-4.0.0 with newlib-1.13.0 for mipsisa32-elf

[Wilson Tsao]

Hi,

I was trying to rebuild the toolchain for mipsisa32-elf. There is an error
when I tried to 
build gcc-4.0.0 with either newlib-1.13.0 or newlib-1.12.0. I have been
building gcc-3.2.1
with newlib-1.12.0 successfully.  Here is the error message:

mipsisa32-elf-ranlib lib.a
make[7]: Leaving directory
`/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/libc/stdlib'
Making all in ctype
make[7]: Entering directory
`/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/libc/ctype'
/tmp/build/gcc/gcc/xgcc -B/tmp/build/gcc/gcc/ -nostdinc
-B/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/ -isystem
/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/targ-include -isystem
/src/gcc-4.0.0/newlib/libc/include -B/gnutools/mipsisa32-elf/bin/
-B/gnutools/mipsisa32-elf/lib/ -isystem /gnutools/mipsisa32-elf/include
-isystem /gnutools/mipsisa32-elf/sys-include  -msoft-float
-DPACKAGE=\"newlib\" -DVERSION=\"1.13.0\"  -I.
-I/src/gcc-4.0.0/newlib/libc/ctype  -O2 -DMISSING_SYSCALL_NAMES -fno-builtin
-O2 -g -O2   -msoft-float -c /src/gcc-4.0.0/newlib/libc/ctype/ctype_.c
/src/gcc-4.0.0/newlib/libc/ctype/ctype_.c:91: error: '_ctype_' aliased to
undefined symbol '_ctype_b+127'
make[7]: *** [ctype_.o] Error 1
make[7]: Leaving directory
`/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/libc/ctype'
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory
`/tmp/build/gcc/mipsisa32-elf/soft-float/newlib/libc'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/tmp/build/gcc/mipsisa32-elf/soft-float/newlib'
make[4]: *** [all-recursive-am] Error 2
make[4]: Leaving directory `/tmp/build/gcc/mipsisa32-elf/soft-float/newlib'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/tmp/build/gcc/mipsisa32-elf/newlib'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/tmp/build/gcc/mipsisa32-elf/newlib'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/tmp/build/gcc/mipsisa32-elf/newlib'
make: *** [all-target-newlib] Error 2
make: Leaving directory `/tmp/build/gcc'

Thanks,

Wilson

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Rebuild gcc-4.0.0 with newlib-1.13.0 for mipsisa32-elf

[Gary Thomas]

On Fri, 2005-05-06 at 15:28 -0700, Wilson Tsao wrote:
> Hi,
> 
> I was trying to rebuild the toolchain for mipsisa32-elf. There is an error
> when I tried to 
> build gcc-4.0.0 with either newlib-1.13.0 or newlib-1.12.0. I have been
> building gcc-3.2.1
> with newlib-1.12.0 successfully.  Here is the error message:
> 

This seems like a GCC or newlib issue, neither of which is part of eCos.
Try sending your problem to more appropriate channels.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Rebuild gcc-4.0.0 with newlib-1.13.0 for mipsisa32-elf

[Jerome Souquieres]

Wilson Tsao wrote:

>Hi,
>
>I was trying to rebuild the toolchain for mipsisa32-elf. There is an error
>when I tried to 
>build gcc-4.0.0 with either newlib-1.13.0 or newlib-1.12.0. I have been
>building gcc-3.2.1
>with newlib-1.12.0 successfully.  Here is the error message:
>  
>
  I tried to build a similar configuration a few days ago: gcc-4.0.0, 
binutils-2.16 and newlib-1.13.0 and had the same failure. From what I 
understand, this is a problem in newlib which uses a kludge no longer 
available in gcc-4.0.0. There is some activity on the newlib CVS to fix 
this problem, so I hope it will be available in the next newlib release.

  FYI, I finally built a mipsisa32-elf toolchain using: binutils-2.16, 
gcc-3.4.3, newlib-1.13.0 and gdb-6.3.
  I didn't take the time yet to check if the resulting toolchain 
produces correct executables though.

  ...Jerome Souquieres...


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss