problem is quite a lot larger than CMake: all
C++ programs will break.
Sincerely,
Sam Trahan
On Tue, Feb 10, 2015 at 4:09 PM, P. A. Cheeseman wrote:
Reading into the final resolution of the IBM ticket tipped me to where the
writev() calls originate in the C++ run-time. The amount
Thanks to all,
Phil
P. A. Cheeseman
ubject: Re: [CMake] Problem writing on GPFS.
>
> P. A. Cheeseman wrote:
> > RedHat and GNU support are on the todo list once I can identify
> > what's in the Cmake source that tricks the run-time into using writev().
> >
> > Several gdb(1) sessions led me to
e the problem.
Best regards,
Phil
P. A. Cheeseman
a...@purdue.edu
765.496.8224
> -Original Message-
> From: Rolf Eike Bee
) calls, with a NULL pointer in
the first iovec entry, also reproduces the behavior. When the
NULL is part of any entry other than the first, the code runs
identically for all storage.
Thanks,
Phil
