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 MinGW (TDM) I used are 64 bits.

Please let me know if you can't get the tgz file. Thanks.

On Mon, Jul 13, 2015 at 2:30 PM, Alan W. Irwin <ir...@beluga.phys.uvic.ca>
wrote:

> 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 anything else.
>
> I enclose the test output with the directory "shared" removed.
> OW my mail wouldn't let me attach the tgz result.
>
> How do I install libplplot.dll if I can't build plplot?
>
> There may simply be too many things different, especially gcc 4.9 vs
> 5.1,
> but I will keep trying things if it will help you improve Plplot.
> ===================================
>
> Hi Walt:
>
> Just to interject here, I believe Orion Poplaski (who extensively
> tests PLplot on Fedora) has largely had success with gcc-5.x, but I
> also recall there was at least one component of PLplot that had to be
> avoided.  Anyhow, with some care I am pretty sure gcc-5.1 will not be
> a problem for you.
>
> Since Arjen is getting good comprehensive test results for
> MinGW-w64/MSYS2 (and also MinGW/MSYS), I am pretty sure that such
> success for TDM cannot be that far away, and your comprehensive test
> results for that platform should indeed help us to diagnose and fix
> (or workaround) whatever small problems that are keeping you from the
> expected success on that platform.
>
> But to make that happens it is essential that you figure out a way to
> communicate the complete comprehensive_test.tar.gz that is generated
> by the script to us.  For example, that missing shared directory in
> your present report tarball contains absolutely essential information
> that helps us debug the error you encountered and if we cannot do that
> in a timely manner also allows us to give you good advice about how to
> workaround that error (say by disabling some component of PLplot).
>
> So please try a mailer without the restriction of disallowing
> subdirectories in outgoing tarball attachments or if you do not have
> access to such a mailer, please post comprehensive_test.tar.gz to a
> website where we can download it for ourselves.  If you decide to use
> the website alternative, each of your report tarballs should be
> located in a directory on your website with a unique name (such as
> "test1", "test2", etc.) so you, Arjen, and I will all know which
> of your report tarballs we are discussing here.
>
> Alan
>
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
>



-- 
Walt Brainerd
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Plplot-general mailing list
Plplot-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-general

Reply via email to