This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hello there, I once made a fully working crossgcc in its default locations (/usr/local) with binutils 2.10.1 gcc 2.95.3 newlib 1.8.2 But now I would like to upgrade to the newer gcc-3.0 as i heard it has better C++ support. I have: P2 333MHz Mandrake Linux 8.0 binutils 2.11.2 gcc 3.0 newlib 1.9.0 Following Bill's pre-crossgcc-faq, i managed to make&install binutils and the gcc-core. but when I try to configure newlib, it says : [(09:59:36) jan@pco449 ~/newbuild]$ ls newlib-1.9.0/ COPYING Makefile.in config.guess* etc/ ltcf-c.sh makefile.vms mpw-README newlib/ ylwrap* COPYING.LIB README config.if gettext.m4 ltcf-cxx.sh missing* mpw-build.in setup.com COPYING.NEWLIB README-maintainer-mode config.sub* install-sh* ltcf-gcj.sh mkdep* mpw-config.in stuff ChangeLog config/ configure* libgloss/ ltconfig* mkinstalldirs* mpw-configure symlink-tree* MAINTAINERS config-ml.in configure.in libtool.m4 ltmain.sh move-if-change* mpw-install texinfo/ [(09:59:41) jan@pco449 ~/newbuild]$ cd m68knewlib [(09:59:46) jan@pco449 ~/newbuild/m68knewlib]$ ll total 0 [(09:59:47) jan@pco449 ~/newbuild/m68knewlib]$ ../newlib-1.9.0/configure --target=m68k-coff Configuring for a i686-pc-linux-gnu host. Created "Makefile" in /home/jan/newbuild/m68knewlib Configuring texinfo... No configuration information in texinfo Configuring etc... creating cache ../config.cache checking for a BSD compatible install... /usr/bin/install -c updating cache ../config.cache creating ./config.status creating Makefile [(10:01:20) jan@pco449 ~/newbuild/m68knewlib]$ If I do a 'make', it seems to head off in the right direction, but it fails which is quite straightforward to me, considering it already spit out a "no configuration information in texinfo" when doing a 'configure'. But to be complete, here is the error that it produces: [for 5 minuts stuff scrolls over the screen, then:] m68k-coff-gcc -B/home/jan/newbuild/m68knewlib/m68k-coff/newlib/ -isystem /home/jan/newbuild/m68knewlib/m68k-coff/newlib/targ-include -isystem /home/jan/newbuild/newlib-1.9.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.9.0\" -I. -I../../../../../newlib-1.9.0/newlib/libc/stdlib -O2 -DMISSING_SYSCALL_NAMES -I../../targ-include -I../../../../../newlib-1.9.0/newlib/libc/../libc/include -fno-builtin -g -O2 -c ../../../../../newlib-1.9.0/newlib/libc/stdlib/div.c m68k-coff-gcc -B/home/jan/newbuild/m68knewlib/m68k-coff/newlib/ -isystem /home/jan/newbuild/m68knewlib/m68k-coff/newlib/targ-include -isystem /home/jan/newbuild/newlib-1.9.0/newlib/libc/include -DPACKAGE=\"newlib\" -DVERSION=\"1.9.0\" -I. -I../../../../../newlib-1.9.0/newlib/libc/stdlib -O2 -DMISSING_SYSCALL_NAMES -I../../targ-include -I../../../../../newlib-1.9.0/newlib/libc/../libc/include -fno-builtin -g -O2 -c ../../../../../newlib-1.9.0/newlib/libc/stdlib/dtoa.c ../../../../../newlib-1.9.0/newlib/libc/stdlib/dtoa.c: In function `_dtoa_r': ../../../../../newlib-1.9.0/newlib/libc/stdlib/dtoa.c:853: Internal compiler error in update_equiv_regs, at local-alloc.c:1097 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. make[3]: *** [dtoa.o] Error 1 make[3]: Leaving directory `/home/jan/newbuild/m68knewlib/m68k-coff/newlib/libc/stdlib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/jan/newbuild/m68knewlib/m68k-coff/newlib/libc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jan/newbuild/m68knewlib/m68k-coff/newlib' make: *** [all-target-newlib] Error 2 [(10:12:17) jan@pco449 ~/newbuild/m68knewlib]$ What do you think is going on? Has m68k-coff been removed from newlib-1.9 ? Or should I first delete ALL previous m68k-coff-* in all directories and the libraries too? Kind regard, Jan PS: this is actually sort of related to my linker-script problem: The first time I made a cross-gcc, I did it the 'old' way by changing the gcc sourcecode. I thought that the linking problem could have been caused by this, so I decided to make a new one. ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |