Re: [Plplot-devel] Space in full pathname issues

[Chris M. <dev...@gm...>]

You could still test the plplot space fixes, but you shouldn't install
cygwin into a location with whitespace in its pathname to do so.

On Fri, May 5, 2017 at 8:34 AM, Arjen Markus <Arj...@de...>
wrote:

> Hi Chris,
>
>
>
> Thanks for the warning – I will not try to test this feature on Cygwin
> then.
>
>
>
> Regards,
>
>
>
> Arjen
>
>
>
>
>
> *From:* Chris Marshall [mailto:dev...@gm...]
> *Sent:* Friday, May 05, 2017 2:25 PM
> *To:* Arjen Markus
> *Cc:* PLplot development list
> *Subject:* Re: [Plplot-devel] Space in full pathname issues
>
>
>
> cygwin doesn't handle install directories with whitespace fully or at all.
>
>
> At any rate, you would not be able to determine if a failure was from
>
> a bad fix at the plplot level or the underlying cygwin and the white space.
>
> Cheers,
>
> Chris
>
>
>
> On Fri, May 5, 2017 at 2:41 AM, Arjen Markus <Arj...@de...>
> wrote:
>
> Hi Alan,
>
>
>
> > -----Original Message-----
> > From: Alan W. Irwin [mailto:ir...@be...
> <ir...@be...>]
> > Sent: Friday, May 05, 2017 5:09 AM
>
> > However, I have figured out two good alternatives for completely testing
> case (4)
> > which are for some tester with access to Windows to install either/both
> the Cygwin
> > and MinGW-w64/MSYS2 platforms using a installation prefix that has a
> blank in the
> > full pathname.  (Something we normally discourage, but we encourage it
> here for
> > this testing
> > purpose.) A PLplot build on either of such platforms would essentially
> provide a
> > complete test of case (4) instead of the piecemeal work you are doing at
> the
> > moment with only some of the external libraries and executables used by
> PLplot
> > having spaces in their full pathname.
> >
> Just a short update: I locally adjusted the diff commands in
> test_diff.sh.in, as these were causing trouble because of spaces in the
> path name. While doing that I found that CMake finds a “diff” program that
> is most probably not compliant with the Linux/POSIX/… conventions. So the
> report about the differences concerns all examples.
>
> The way around that is to force the use of the MinGW-w64/MSYS2 diff
> program. There may be more such surprises.
>
> And then there is the matter of the mysterious “D?” directory created by
> ctest. It is not the consequence of anything obvious that I could detect.
>
> Especially this latter issue hinders progress in the comprehensive tests,
> as it causes a premature end (find is not able to handle this directory and
> thus an error is thrown). So slow progress for the moment.
>
> Regards,
>
> Arjen
>
> DISCLAIMER: This message is intended exclusively for the addressee(s) and
> may contain confidential and privileged information. If you are not the
> intended recipient please notify the sender immediately and destroy this
> message. Unauthorized use, disclosure or copying of this message is
> strictly prohibited. The foundation 'Stichting Deltares', which has its
> seat at Delft, The Netherlands, Commercial Registration Number 41146461, is
> not liable in any way whatsoever for consequences and/or damages resulting
> from the improper, incomplete and untimely dispatch, receipt and/or content
> of this e-mail.
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>
>
> DISCLAIMER: This message is intended exclusively for the addressee(s) and
> may contain confidential and privileged information. If you are not the
> intended recipient please notify the sender immediately and destroy this
> message. Unauthorized use, disclosure or copying of this message is
> strictly prohibited. The foundation 'Stichting Deltares', which has its
> seat at Delft, The Netherlands, Commercial Registration Number 41146461, is
> not liable in any way whatsoever for consequences and/or damages resulting
> from the improper, incomplete and untimely dispatch, receipt and/or content
> of this e-mail.
>