Re: [Fixinclude]: Fix typo and default to twoprocess on VMS

2012-04-24 Thread Tristan Gingold
On Apr 18, 2012, at 8:23 PM, Bruce Korb wrote: > Hi, > > When I approved a patch in 2008, there was a typo. I didn't > notice and it was "fixed" by removing a formatting element. > Your patch corrects the error. > > Please apply your changes to active branches. Thank you! > Regards, Bruce Th

Re: [Fixinclude]: Fix typo and default to twoprocess on VMS

2012-04-18 Thread Bruce Korb
Hi, When I approved a patch in 2008, there was a typo. I didn't notice and it was "fixed" by removing a formatting element. Your patch corrects the error. Please apply your changes to active branches. Thank you! Regards, Bruce

Re: [Fixinclude]: Fix typo and default to twoprocess on VMS

2012-04-18 Thread Tristan Gingold
On Apr 17, 2012, at 4:21 PM, Bruce Korb wrote: > Hi Tristan, > > On Tue, Apr 17, 2012 at 5:57 AM, Tristan Gingold wrote: >> Hi, >> >> one-process methodology cannot be used on VMS[...] >> But, when twoprocess is selected, gcc emits a warning[...] >> Ok for trunk ? > >> diff --git a/fixinclude

Re: [Fixinclude]: Fix typo and default to twoprocess on VMS

2012-04-17 Thread Bruce Korb
Hi Tristan, On Tue, Apr 17, 2012 at 5:57 AM, Tristan Gingold wrote: > Hi, > > one-process methodology cannot be used on VMS[...] > But, when twoprocess is selected, gcc emits a warning[...] > Ok for trunk ? > diff --git a/fixincludes/configure.ac b/fixincludes/configure.ac > index e7de791..f1fb2

[Fixinclude]: Fix typo and default to twoprocess on VMS

2012-04-17 Thread Tristan Gingold
Hi, one-process methodology cannot be used on VMS because fork/pipe/dup2 aren't fully supported. To avoid a build failure, it is therefore better to build using two-process methodology. But, when twoprocess is selected, gcc emits a warning due to a missing specifier in printf. The patch fixe