Hello On 29.03.11, you wrote:
>> >> This sounds like the generic Cygwin fork-error/BLODA problem and not >> specific to GCC. > > Indeed. For what it's worth, gcc itself *does* use the Cygwin spawn* > functions > to avoid this problem, but (curiously) the Cygwin versions of make, bash, and > expect do not. Therefore the problem can still be seen during a build. 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 ? static pi d_t win32_spawn (const char *executable, I add now an error in pex_unix.c, and compile file.so cygwin build use vfork stuff. static pid_t pex_unix_exec_child (struct pex_obj *obj, int flags, const char *executable, I try to build a gprof build, but i dont know what options i need set for GCC build and if gprof work on cygwin. this is in config.log $ /bernd/gcc4/configure --target=m68k-amigaos --with-cpu=m68040 --prefix=/usr/local/amiga ... configure:2429: checking build system type configure:2443: result: i686-pc-cygwin configure:2490: checking host system type configure:2503: result: i686-pc-cygwin configure:2523: checking target system type configure:2536: result: m68k-unknown-amigaos configure:2590: checking for a BSD-compatible install configure:2658: result: /usr/bin/install -c > > > r~ Regards
