Vms doesn't have fork.
It does have vfork/exec.
Fixincludes uses fork.
It appears fixincludes uses it in two ways:
1) can be replaced by vfork?
2) subject to configuration and easily avoided
Really -- I would suggest just use the more portable form in the case of #2 and
don't bother with any need to configure anything. It is to much slower to be
worth any hassle?
As well, libiberty's pex might be useful here -- to replace (v)fork/exe use.
I have an obvious two line patch but it is not yet tested -- fork -> vfork and
add a line to autoconf.
Also the two lines that check for x86-mingw and x86_64-mingw should just check
for mingw imho.
--
Summary: fixincludes fork vs. vms
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jay dot krell at cornell dot edu
GCC build triplet: i686-apple-darwin9
GCC host triplet: alpha-dec-vms
GCC target triplet: alpha-dec-vms
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44252
