Hi Arjen,
>
> I think I found the cause: it was a bit hidden in directories I
> normally
> don't look at: I had a special CMake module for gfortran in
> cmake/Modules/Platform. I never committed it, apparently, but now I
> have.
That explains a lot ;)
>
> Could you check if that makes dlltool su
Hi Werner,
>
> Arjen, btw, in cygwin I have the same problem with the fortran 77
> compiler (no import library created for libplplotf77d-9.1.1.dll) when I
> add -DBUILD_TEST=ON. Can you confirm that?
>
I have solved the problem (not committed yet): I introduced a file
Cygwin-GNU-Fortran.cmake
Hi Werner,
I think I found the cause: it was a bit hidden in directories I normally
don't look at: I had a special CMake module for gfortran in
cmake/Modules/Platform. I never committed it, apparently, but now I
have.
Could you check if that makes dlltool superfluously for you? If so,
we can simp
Hi Werner,
On 2009-03-31 09:04, Werner Smekal wrote:
> Hi Arjen,
>
>>
>> I realised that something like this was going wrong by manually running
>> it with various arguments and extra print-statements.
>
> Interesting, I did the same, but there was nothing printed on the screen
> ever until I a
Hi Arjen,
> Well, I solved the problem: it turns out that Werner was on the right
> track - I needed to expand the PATH environment variable, not with
> the drivers subdirectory that contains the DLLs, but with the src
> subdirectory, as apparently "test-drv-info" links to
> "libplplot-9.6.1.dll"!
Hi Werner,
I think it is not just a problem with Cygwin: quite frequently
the only error message from a program that can not run for lack
of a DLL is that it immediately returns. I am not sure under
what circumstances this happens, but I think the following scenario
provides them:
Program A depen
Hi Alan,
On 2009-03-30 19:44, Alan W. Irwin wrote:
>
> It's a long shot, but there was some purpose to my question. So please
> answer it with the _exact_ command (test-drv-info + argument), that was run
> by make VERBOSE=1 including the directory the command was run in.
>
> test-drv-info is
Hi Alan,
>
> What I find disconcerting about Arjen's error report is the lack of
> error
> message (other than no output) when test-drv-info could not find the
> PLplot
> library. If I arrange that case on Linux by temporarily renaming
> the PLplot
> library, test-drv-info generates the fol
On 2009-03-30 22:10+0200 Werner Smekal wrote:
> I know what the problem is, but a solution is not straight forward.
> [..]I already did some changes and will commit later, so that cygwin works
> similar to the other Win32 compiler toolsets (all dlls are in dll directory,
> and plplot just opens
Hi Alan and Arjen,
> Hi Arjen:
>
> It's a long shot, but there was some purpose to my question. So please
> answer it with the _exact_ command (test-drv-info + argument), that was run
> by make VERBOSE=1 including the directory the command was run in.
>
> test-drv-info is simply a renamed version
On 2009-03-30 11:20+0200 Arjen Markus wrote:
> I ran test-drv-info manually, there was no output to the screen.
> (I saw that from the empty .rc file appearing in the "test-drivers" (if
> I remember the name correctly) subdirectory as well).
>
>>
>> Please run test-drv-info by hand (don't forget
Hello Alan, Werner,
On 2009-03-27 17:16, Alan W. Irwin wrote:
> On 2009-03-27 10:20+0100 Arjen Markus wrote:
>
>> Hi,
>>
>> the new set-up to get the driver .rc files seems to be
>> failing under Cygwin. I have no idea why: I am not overly
>> familiar with libtool and its inner workings, but what
On 2009-03-27 10:20+0100 Arjen Markus wrote:
> Hi,
>
> the new set-up to get the driver .rc files seems to be
> failing under Cygwin. I have no idea why: I am not overly
> familiar with libtool and its inner workings, but what
> happens is this:
>
> The test-drv-info runs to completion but writes
Hi Werner,
well, the DLLs are in the same directory, and the test-drv-info
program explicitly loads them. So, I would expect that failure
to find results in an error message (induced by a NULL pointer)
rather a silent stop.
Regards,
Arjen
On 2009-03-27 10:35, Werner Smekal wrote:
> Hi Arjen,
>
Hi Arjen,
does cygwin find the dlls, i.e. is the dll directory with the dynamic
drivers in the PATH? It's still Windows ;).
Regards,
Werner
On 27.03.2009, at 10:20, Arjen Markus wrote:
> Hi,
>
> the new set-up to get the driver .rc files seems to be
> failing under Cygwin. I have no idea why:
15 matches
Mail list logo
