[Plplot-devel] MacOS X tests

[Rafael L. <rla...@us...>]

* Alan W. Irwin <ai...@us...> [2003-12-28 09:10]:

> On 2003-12-28 10:28+0100 Michel Peyrard wrote:
> 
> >
> >  I tried to compile plplot with the new tarfile (20031227) on Mac OS X
> > 10.3.
> > I attach below the results of the ./configure command and the end of the
> > output of make with different options.
> 
> I am glad you have been able to find workarounds so that you can test the
> present series of cvs snapshots rather than working with the old 5.2.1.
> 
> Unfortunately, my fortran linking configuration fixes were committed
> slightly too late to be in the latest cvs snapshot tarball.  So you will
> have to wait for the next one to avoid (I hope) the fortran linking
> workarounds you have to do at the present time.  Rafael has suggested on
> this list that he wait until I finish all my fortran example extensions
> work before he makes another snapshot tarball. It is hard to say, but I
> think that may be another 3 days full time.  Of course, he is free to make
> a test tarball earlier so we can find out immediately if the configuration
> changes work for you for the present fortran examples, but that is up to
> him.

Okay, I will try to generate a new test tarball soon.

> Assuming the fortran configuration fixes solve your fortran linking
> problem, then on past experience with Mac OS X, shared libraries should
> work (in fact they should work now if you specify --disable-f77), but there
> is still one more bug in get-drv-info on Mac OS X that can only be worked
> around at the present time by using --disable-dyndrivers on that platform.
> If you want to help Rafael solve that one, here is what he needs to start
> (for a configure without the --disable-dyndrivers option):
> 
> "This is a very strange bug, indeed, and I have no clue about its origin.
> It is perhaps a libtool bug that is triggered on the Mac OS X system. Could
> you please run:
> 
> make 2>&1 > ../build.log
> 
> and send the resulting build.log to me?"

I am already trying to debug this with the help from Koen van der Drift.

> > Final remark: the output of the configure command does not write the
> > command that was typed after command:  . I think that previous versions
> > did write the command.
> 
> I noticed that as well.  I believe that was inadvertently removed by one of
> recent configuration changes.  Rafael, could you please put that back in?

Done in CVS.

-- 
Rafael