https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62296
--- Comment #3 from Harald Anlauf <anlauf at gmx dot de> --- (In reply to Dominique d'Humieres from comment #2) > On x86_64-apple-darwin13.3, for the test in comment 1 I get > > 0 0 '' > sh: /bin/false: No such file or directory > 127 0 '' > sh: /nosuchfile: No such file or directory > 127 0 '' > 0 > sh: /bin/false: No such file or directory > 127 > sh: /nosuchfile: No such file or directory > 127 > > From > https://groups.google.com/forum/?hl=en#!topic/comp.lang.fortran/6ymZIb6flDg > it seems that you are expecting too much of the EXECUTE_COMMAND_LINE options. Probably. I'm now wondering why EXECUTE_COMMAND_LINE was standardized in a way that allows for ambiguous implementations without any reliable advantage over the non-standard "SYSTEM" implementations. One might be able to do better on any reasonable Unix/Linux system.
