Re: [Plplot-general] Including cairo driver

[Alan W. I. <ir...@be...>]

On 2014-05-04 09:12-0700 Walt Brainerd wrote:

> Alan: do you really want to look at the results
> of my build attempts? It seems quite obvious that
> there is something "wrong" with my system
> configuration or the way I am trying to do things.

Yes, please.  Often the PLplot build problem is something really simple, but we
cannot help you figure that out without comprehensive information from
you containing all the details.  Only some of those details will be
relevant, but we don't know which until we see all of them. Without
such comprehensive details, we speculate as to what the issue is, you
respond, we speculate again, etc., and those iterations consume
a lot of time for both parties.

So here is the comprehensive information that I would really like to
see in a typical bug report from you and others here so that we have a
good chance to help you while minimizing iterations.

1. List all environment variables.  (This is important since some of
those environment variables affect cmake's operation.) On Unix or if
you have MSYS installed this can be done with

printenv >printenv.out

but otherwise, output any PATH, CMAKE_LIBRARY_PATH,
CMAKE_INCLUDE_PATH, PKG_CONFIG_PATH, CC, CXX, FC, CFLAGS, CXXFLAGS, and FFLAGS
environment variables you have set to a file, and include that file in
your bug report.

2. Give the exact command you used to invoke cmake.

3. Give the output from that command captured, e.g., in the cmake.out file
using

cmake <whatever options> <source tree> >& cmake.out

where <whatever options> and <source tree> are given in detail in 2.

The above is a good way to capture stderr and stdout in a file
simultaneously on Unix, Cygwin, or for MSYS, but I am sure there is also
a way to capture stderr and stdout for a cl-based native Windows environment,
but I don't know what that is.

4. Include the resulting CMakeCache.txt file (from the top directory in the
build tree).

5. Give the exact build command you used (with VERBOSE=1 set)

For example, on Unix, Cygwin, or MSYS that could be

make VERBOSE=1 all >& all.out

and on native Windows it would be

nmake VERBOSE=1 all >& all.out

(where ">&" stands symbolically for whatever means are necessary to
capture stderr and stdout on Windows in the all.out file).

6. Give the output from the build command (e.g., all.out in the example just above).

Then collect all these requested files in a compressed tarball and
send it to this list along with the cmake and build command invocation
information requested in 2 and 5.

I hope these detailed instructions for reporting any PLplot build
problems will be a help to you and everyone else on this list.

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
__________________________