This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi! > Do you have experience with binutils for 2.9.1 PowerPC/EABI target > working under Windows NT (Intel)? > > I have a problem during building. > > I have performed the following steps under Windows NT v.4.0 (build 1381: > > Service Pack 3): > > 1. Install Cygnus CDK beta 19. > 2. Install Cygnus CDK beta 19.1 update. > 3. Lauch bash-2.01. > 4. Issue the following command from binutils 2.9.1 > source directory: "./configure --target=powerpc-eabi". > 5. Lauch make and received the following error > message: > ---------------------- > bash-2.01$ make > ... > gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. > -I. -I../bfd -I./config -I./../include -I./.. > -I./../bfd -g -O2 -c ./config/tc-ppc.c > (C:\Cygnus\B19\H-i386-cygwin32\lib\gcc-lib\ > i386-cygwin32\2.7-B19\cc1.exe 1067) Exception: > STATUS_ACCESS_VIOLATION (C:\Cygnus\B19\ > H-i386-cygwin32\lib\gcc-lib\i386-cygwin32\ > 2.7-B19\cc1.exe 1067) Dumping stack trace to > cc1.exe.core > gcc: Internal compiler error: program cc1 got fatal signal 0 > make[1]: *** [tc-ppc.o] Error 1 > make: *** [all-gas] Error 2 > ---------------------- > > May you be so kind as to recommend what is wrong? It looks like the > problem may be connected with "cc1.exe", "tc-ppc.c" or Windows NT > environment. Yeah, this is due to the optimize flag. CC doesn't manage to compile this file with -O2 go to the directory where tc-ppc.c, and copy the line used to compile it but replace -O2 by -O0 It should compile well Then retype: make and everything just go fine! Best regards, Geoffroy _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com