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]

Re: binutils 2.9.1 for PowerPC/EABI under Windows NT


I have built binutils-2.9.1 for PowerPC/EABI on my WindowsNT4.0 SP3
machine enhanced with cygwin32 19.1. I had some problems, I remember
one where I had to remove optimization flags from the makefile and
compile that single file (the same file as in your example?). Then I 
reinserted the optimization flags for the rest of the build.

So try to compile this ./config/tc-ppc.c file without optimization.

But my biggest problem was that I didn't have the cygwin19 sh.exe
as my /bin/sh.exe program. That caused many weird problems during
configuration.
--
	Ola Liljedahl
	olli@enea.se
	Enea OSE Systems

On Thu, 2 Jul 1998, Yaroslav Domaratsky wrote:

> Hello All,
> 
> 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.
> 
> Thanks in advance,
> Yaroslav
> 
> 
> 
>