Mail Archives: cygwin/1998/03/06/14:15:35
Tim Park wrote:
> - Make, upon seeing .EXPORT_ALL_VARIABLES:, gave two of these:
>
> (J:\BIN\SH.EXE 1030) Exception: STATUS_ACCESS_VIOLATION
> (J:\BIN\SH.EXE 1030) Dumping stack trace to SH.EXE.core
I'm seeing the same thing, and have generated a small makefile
that triggers this repeatably:
%.dep: %.c
gcc -traditional -E -M $< | sed -e 's!$*\.o!$*.o $@!' > $@
Now just create a blorp.c file with anything in it and do
gmake blorp.dep. I see:
~/LANL/JTpack90/b19$ gmake blorp.dep
gcc -traditional -E -M blorp.c | sed -e 's!blorp\.o!blorp.o blorp.dep!' > blorp.dep
(C:\BIN\SH.EXE 1034) Exception: STATUS_ACCESS_VIOLATION
(C:\BIN\SH.EXE 1034) Dumping stack trace to SH.EXE.core
cpp.exe: output pipe has been closed
The command works fine when executed by hand at the bash command
line:
~/LANL/JTpack90/b19$ gcc -traditional -E -M blorp.c | sed -e 's!blorp\.o!blorp.o blorp.dep!' > blorp.dep
~/LANL/JTpack90/b19$ cat blorp.dep
blorp.o blorp.dep: blorp.c
~/LANL/JTpack90/b19$
Note that /bin/sh.exe is a copy of bash.exe.
Any ideas?
Thanks,
-John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -