Hello 

On 30.03.11, you wrote:

> Bernd Roesch <nospamn...@gmx.de> writes:
> 
>> I add an error in file libiberty/pex-win32.c to check if cygwin build use 
>> win32_spawn.
>> but gcc compile ok, so it seem that cygwin build do not use pex-win32.c.Or 
>> need i set a compile
>> option for GCC ?
> 
> The choice is determined in libiberty/configure.ac:
> 
>     *-*-mingw* | *-*-winnt*)  pexecute=pex-win32  ;;
>     *-*-msdosdjgpp*)      pexecute=pex-djgpp  ;;
>     *-*-msdos*)       pexecute=pex-msdos  ;;
>     *)                pexecute=pex-unix   ;;
> 
> It may be appropriate to use pex-win32 for *-*-cygwin*.  I don't know,
> as I am not a cygwin user myself.

thanks, i add this in configure too, i clear whole objdir, do configure and 
make and i see libiberty
obj dir contain now a pex-win32.o file and no pex-unix.o file.

Compile of GCC package fail when libgcc should compile with the new create xgcc 
compiler.

I install then the compiler files and do a testcompile with netsurf to see more 
errors, but it not
work too.I get only this
message.both new files are in bin dir.maybe somebody can help what i need 
change more, so i can
test if GCC work same fast as with 1 CPU core, when all cores are enable.

 COMPILE: content/content.c
m68k-amigaos-gcc: couldn't run 'm68k-amigaos-gcc-4.5.0': CreateProcess: No
file or directory
make: *** [build-CYGWIN_NT-6.1-WOW64-amigaos3/content_content.o] Error 1

i see on this message, seem GCC do for every compiler run create 2 threads.
1. gcc create gcc-4.5.0.
2. gcc4.5.0 create cc1

so if pex_win is faster, can give high speedup. 

this is what i add in libiberty/configure and libiberty/configure.ac

case "${host}" in
      *-*-cygwin* | *-*-mingw* | *-*-winnt*)         pexecute=./pex-win32.o  ;;
     *-*-msdosdjgpp*)       pexecute=./pex-djgpp.o  ;;
     *-*-msdos*)        pexecute=./pex-msdos.o  ;;
     *)             pexecute=./pex-unix.o   ;;
esac



> 
> Ian
Regards

Reply via email to