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]

Binutils 2.9 for PPC under cygwin32 B19

Hi to all!
	I shall be very thankfull to everybody who will be able to solve the
following problem of compiling binutils 2.9 for PowerPC in cygwin32
(version B19) environment: compilation fails on tc-ppc.c file of gas with
cc1 exeption STATUS_ACCESS_VIOLATION. The following dump is produced (if it
may help):
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) Exception trapped!
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) exception C0000005 at 51DCE0
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) exception: ax 0 bx 0 cx 0 dx 0
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) exception: si 487F24C di 0 bp 26BF39C sp 26BF384
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) exception is: STATUS_ACCESS_VIOLATION
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) Stack trace:
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 0: sp = 0x26BF094, pc = 0x1000A26C
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 1: sp = 0x26BF1B8, pc = 0xBFF7663C
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 2: sp = 0x26BF1DC, pc = 0xBFF859FA
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 3: sp = 0x26BF274, pc = 0xFFECBAD7
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 4: sp = 0x26BF39C, pc = 0x51DE4A
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 5: sp = 0x26BF3D4, pc = 0x51E2C3
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 6: sp = 0x26BF418, pc = 0x51E39E
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 7: sp = 0x26BF428, pc = 0x5187AE
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 8: sp = 0x26BF500, pc = 0x42AB17
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 9: sp = 0x26BF538, pc = 0x418646
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 10: sp = 0x26BF55C, pc = 0x407AC5
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 11: sp = 0x26BFA68, pc = 0x429B92
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 12: sp = 0x26BFA90, pc = 0x42C8D2
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 13: sp = 0x26BFAD8, pc = 0x10006B59
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 14: sp = 0x26BFE0C, pc = 0x10006B6C
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) frame 15: sp = 0x26BFE18, pc = 0x52B0A5
(C:\CYGNUS\B19\H-I386-CYGWIN32\LIB\GCC-LIB\I386-CYGWIN32\2.7-B19\CC1.EXE
1084) End of stack trace (more stack frames may be present)

	Another question is - why my attempt to make target as ppc-rtems-coff was
rejected? Isn't it a most widespread file format?

	Thanks for replies.
                                Dr.Leon M.Pollak
                                       Director
                         PLR Information Systems Ltd.
                            E-mail: leonp@plris.com