On 2016-12-13 10:18- Arjen Markus wrote:
> To get all the details, see the attached tarball.
Hi Arjen:
I have now had a chance to look at those detailed results (only for shared case
and only for ctest in build tree), and all seems fine. And because
you specified
--do_submit_dashboard yes
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Tuesday, December 13, 2016 12:13 PM
>
> I am very happy to hear that. Big sigh of relief!
>
> Since I currently have comprehensive test success on Linux and you now also
> have
> that on Cygw
On 2016-12-13 10:18- Arjen Markus wrote:
> The short report is: your solution worked!
I am very happy to hear that. Big sigh of relief!
Since I currently have comprehensive test success
on Linux and you now also have that
on Cygwin, would you be willing to follow up
with a comprehensive tes
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> Hi Arjen:
>
> The short story is I am looking forward to your next report.
>
The short report is: your solution worked!
> Here is the longer story.
>
To get all the details, see the attached tarba
On 2016-12-12 08:30- Arjen Markus wrote:
> Hi Alan,
>
>
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>> Sent: Sunday, December 11, 2016 11:25 PM
>>
>> Unfortunately, those compiler warnings in the report about "redeclared
>> without
>> dllimport at
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Sunday, December 11, 2016 11:25 PM
>
> Unfortunately, those compiler warnings in the report about "redeclared without
> dllimport attribute" (and eventual build failure for the qt device driver
On 2016-12-11 15:04- Arjen Markus wrote:
>> -Original Message-
>> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>>
>> DONE as of commit 6b01000. I would appreciate you trying the identical
>> comprehensive test check on Cygwin to confirm the pyqt4 issue you were
>> seeing is
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> DONE as of commit 6b01000. I would appreciate you trying the identical
> comprehensive test check on Cygwin to confirm the pyqt4 issue you were seeing
> is
> now gone.
>
I did an update of the re
On 2016-12-08 10:42-0800 Alan W. Irwin wrote:
> Hi Arjen:
>
> On 2016-12-08 07:59- Arjen Markus wrote:
>
>> This visibility issue is one of obscurer aspects of today's
> programming experience. It is akin to the import/export circus in
> Windows DLLs. Always good for some puzzles.
>
> Yes, and
Hi Arjen:
On 2016-12-08 07:59- Arjen Markus wrote:
> This visibility issue is one of obscurer aspects of today's
programming experience. It is akin to the import/export circus in
Windows DLLs. Always good for some puzzles.
Yes, and I have figured out this particular puzzle. :-) The code gen
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Wednesday, December 07, 2016 10:10 PM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: RE: plplot_pyqt4 shared object build issue
>
> Hi Arjen:
>
> Never mind about my request for yo
Hi Arjen:
Never mind about my request for you to do some nm experiments. (Although you
might want to do those experiments in any case just to familiarize yourself with
this very helpful tool for figuring out such undefined reference issues.)
>From my recent experiments here, I am virtually posit
On 2016-12-07 08:43- Arjen Markus wrote:
> Here is the report from the comprehensive test script. A link error
on PyQt4 made it stop prematurely. I will take the other steps on
Friday.
Hi Arjen:
Thanks for that quick response. As you could tell it is the same
undefined reference result for
Hi Alan,
Here is the report from the comprehensive test script. A link error on PyQt4
made it stop prematurely. I will take the other steps on Friday.
Regards,
Arjen
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Wednesday, December 07, 2016
Hi Alan,
I probably have time today to run the test script without -j4. The other things
I do not know. The problem with the -j option occurs in MinGW-w64/MSYS, not in
Cygwin, unless I am mistaken. But I will do this anyway, just to make sure.
(Getting the results from nm will take more of
On 2016-12-01 08:31- Arjen Markus wrote:
[...]
I am not sure about the PyQt4 component. But
when I tried to do it via the comprehensive test script, I got
compilation errors - see the attached tarball.
Hi Arjen:
Now that I have finally had a chance to look at your report, it
appears to m
16 matches
Mail list logo
