On 2019-12-24 13:51+0100 Xavier Cardil wrote:
I am now porting a program from Python to C++ that uses Plplot
Getting this error when running Cmake in my project :
[cmake] CMake Error at lib/plplot.git/CMakeLists.txt:60
(cmake_minimum_required):
[cmake] CMake 3.13.2 or higher is required. Yo
On 2019-12-24 15:25+0100 Xavier Cardil wrote:
Nevermind, I solved the problem, sorry for the mess !
No problem. Just out of curiosity what did you do to make your
approach (with PLplot a subproject of your own project) work?
Alan
__
Alan W. Irwin
Programming affilia
Nevermind, I solved the problem, sorry for the mess !
On Tue, Dec 24, 2019 at 1:51 PM Xavier Cardil
wrote:
> I am now porting a program from Python to C++ that uses Plplot
>
> Getting this error when running Cmake in my project :
>
> [cmake] CMake Error at lib/plplot.git/CMakeLists.txt:60
> (cma
On 2018-09-12 19:46+0100 Phil Rosenberg wrote:
Hi Alan
I think I have fixed it. In fact it turned out that test-drv-info was
doing exactly what it should.
running ldd on the wxwidgets.so file revealed 3 dependencies that
could not be found.
The flavour of Linux I am building on is Arch,
whic
Hi Alan
I think I have fixed it. In fact it turned out that test-drv-info was
doing exactly what it should.
running ldd on the wxwidgets.so file revealed 3 dependencies that
could not be found. The flavour of Linux I am building on is Arch,
which maintains rolling upgrades of all packages rather t
On 2018-09-11 20:07+0100 Phil Rosenberg wrote:
Hi Alan
I just wanted to let you know that your recent commit seems to have fixed all
the strange output I was getting at the end of my cmake command.
Hi Phil:
I was very happy to receive that encouraging news concerning all the
build-system
imp
Hi Alan
I just wanted to let you know that your recent commit seems to have fixed all
the strange output I was getting at the end of my cmake command.
I am still getting a build arror though
Generating test_dyndrivers_dir/wxwidgets.driver_info
Could not open driver module
/home/users/prosenberg01/
On 2015-07-15 13:24-0700 Walt Brainerd wrote:
> First, yes, those are the correct compilers:
>
> bash-3.1$ which gfortran
> /c/mingw/bin/gfortran.exe
> bash-3.1$ gfortran --version
> GNU Fortran (tdm64-1) 5.1.0
>
> I tried MSYS2 to see what would happen.
> Nothing works--not even git. Says my
> ve
I need another bit of information.
I have mingw (the TDM version) with the compilers,
msys\1.0, msys64 (msys2), and cygwin.
Obviously, the mingw is necessary. Which of the others
should be accessible when running the test?
I think when I compiled 5.10 with gcc 4.9, I had none
of them accessible
First, yes, those are the correct compilers:
bash-3.1$ which gfortran
/c/mingw/bin/gfortran.exe
bash-3.1$ gfortran --version
GNU Fortran (tdm64-1) 5.1.0
I tried MSYS2 to see what would happen.
Nothing works--not even git. Says my
version of cygwin.dll is incompatible.
(Incompatible with what? The
On 2015-07-13 15:55-0700 Walt Brainerd wrote:
> Sorry, I saw all the examples in the shared directory and thought
> maybe they were not necessary. Try this:
>
> http://www.fortran.com/Test1/c_d_t.tgz
Hi Walt:
I was able to download that Test1 report tarball.
Here are my comments on the results
Sorry, I saw all the examples in the shared directory and thought
maybe they were not necessary. Try this:
http://www.fortran.com/Test1/c_d_t.tgz
And I thought maybe the reason for the problem with the DLL
might be 32 vs 64 bits ??? But I will just leave it to you experts.
The compilers in the M
Walt said:
===
Here are my attempts to run the test as you requested.
Just to get all the facts:
The TDM version of Mingw is in C:\mingw.
It includes gcc version 5.1.
Msys is in C:\msys\1.0--the MSYS web site implied this
was not the latest, but I couldn't find a
> because it will throw away anything in the test directory), is that it
> collects as much information as could be relevant from the environment.
> That will save us some time ;).
>
>
>
> Regards,
>
>
>
> Arjen
>
>
>
>
>
>
>
> *From:* Arjen Ma
as could be relevant from the environment. That will save us some
time ;).
Regards,
Arjen
From: Arjen Markus
Sent: Monday, July 13, 2015 1:18 PM
To: Arjen Markus; Walt Brainerd
Cc: plplot_general
Subject: RE: [Plplot-general] Problem building 5.11 on Windows 8.1
Hi Walt,
The link prob
: Re: [Plplot-general] Problem building 5.11 on Windows 8.1
Hi Walt,
I had to reinstall MinGW 64-bits, as indeed it was hardly useable. I have done
so by installing MSYS2 as recommended by Alan. Now I see problems with the .def
file for the Fortran libraries - it has to do with the calling
: plplot_general
Subject: Re: [Plplot-general] Problem building 5.11 on Windows 8.1
Hi Walt,
I had to reinstall MinGW 64-bits, as indeed it was hardly useable. I have done
so by installing MSYS2 as recommended by Alan. Now I see problems with the .def
file for the Fortran libraries - it has to do with
Arjen Markus
Cc: plplot_general
Subject: Re: [Plplot-general] Problem building 5.11 on Windows 8.1
Alan: mingw-64 etc. does not yet include gcc 5.1;
that is why I am using the TDM version.
Arjen: with the new version, plplot builds (the static
library version), but when I run it, I get all kinds of
e
Markus; plplot_general
Subject: Re: [Plplot-general] Problem building 5.11 on Windows 8.1
I know that Plplot "works". However,
I intend to include gcc 5.1 with the next Fortran Tools
and would like to include Plplot.
If Plplot is built with Cygwin or any MinGW that does not
have gcc 5.1, p
I know that Plplot "works". However,
I intend to include gcc 5.1 with the next Fortran Tools
and would like to include Plplot.
If Plplot is built with Cygwin or any MinGW that does not
have gcc 5.1, plplot will not work with any Fortran program
compiled with gfortran 5.1 because the *.mod files a
On 2015-07-10 14:00-0700 Alan W. Irwin wrote:
> On 2015-07-10 12:27-0700 Walt Brainerd wrote:
>
>> Alan: mingw-64 etc. does not yet include gcc 5.1;
>> that is why I am using the TDM version.
>
> Understood for your normal use case. But you should not need gcc 5.1
> just to test that PLplot is wo
On 2015-07-10 12:27-0700 Walt Brainerd wrote:
> Alan: mingw-64 etc. does not yet include gcc 5.1;
> that is why I am using the TDM version.
Understood for your normal use case. But you should not need gcc 5.1
just to test that PLplot is working. So my point remains for the
special case of repor
y, July 10, 2015 10:37 AM
> *To:* Walt Brainerd; plplot_general
> *Subject:* Re: [Plplot-general] Problem building 5.11 on Windows 8.1
>
>
>
> Hi Walt,
>
>
>
> I am trying this myself – using the comprehensive tests script under MSYS
> – and I ran into the same issue. It se
ccess() function. With this latest version it
>> ought to work for you too.
>>
>>
>> Regards,
>>
>>
>>
>> Arjen
>>
>>
>>
>>
>>
>> *From:* Arjen Markus [mailto:arjen.mar...@deltares.nl]
>> *Sent:* Friday, July 10
37 AM
> *To:* Walt Brainerd; plplot_general
> *Subject:* Re: [Plplot-general] Problem building 5.11 on Windows 8.1
>
>
>
> Hi Walt,
>
>
>
> I am trying this myself – using the comprehensive tests script under MSYS
> – and I ran into the same issue. It seems that the logic
To: Walt Brainerd; plplot_general
Subject: Re: [Plplot-general] Problem building 5.11 on Windows 8.1
Hi Walt,
I am trying this myself - using the comprehensive tests script under MSYS - and
I ran into the same issue. It seems that the logic for including the header
file unistd.h is incomplete
Hi Walt,
I am trying this myself - using the comprehensive tests script under MSYS - and
I ran into the same issue. It seems that the logic for including the header
file unistd.h is incomplete or incorrect as far as MinGW is concerned. I have
changed this in my own repository to:
#include
On 2015-07-09 16:24-0700 Walt Brainerd wrote:
> I have the TDM version of MinGW installed.
>
> C:\Users\Walt>gfortran --version
> GNU Fortran (tdm64-1) 5.1.0
> Copyright (C) 2015 Free Software Foundation, Inc.
>
> I downloaded 5.11.0 using git and built with the following
> (all one line, of cours
28 matches
Mail list logo
