[CMake] Problem writing on GPFS.

[Rolf Eike Beer]

P. A. Cheeseman wrote:
>      System: RHEL6   (2.6.32-504.8.1.el6.x86_64)
>      Hardware: Various cluster nodes.

>      A C code with explicit writev() 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.

I would suggest contacting Red Hat. This sounds for me like a bug in the GPFS 
code, especially since the call succeeds if the (NULL, 0) pair is in a later 
pair.

Other than that, I don't see a reason why g++ should emit such a call. Should 
probably be reported to the gcc guys. Or maybe this is just something in your 
libc, so gcc isn't at fault at all. Probably time for the Red Hat guys to 
investigate, too ;)

Eike
-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://public.kitware.com/pipermail/cmake/attachments/20150210/2d9545aa/attachment.sig>