yes of course: here is a cut-and-paste:

cd pgplot_build [the directory I created for building]

make xwin
[  0%] Built target plhershey-unicode-gen
[  7%] Built target plhershey-unicode.h_built
[  7%] Built target csirocsa
[ 15%] Built target deltaT-gen
[ 15%] Built target deltaT.h_built
[ 15%] Built target tai-utc-gen
[ 15%] Built target tai-utc.h_built
[ 15%] Built target qsastime
[ 92%] Built target plplotd
[100%] Built target xwin

make _plplotcmodule_fixed
make: *** No rule to make target `_plplotcmodule_fixed'.  Stop.


On 1 May 2014 18:34, Alan W. Irwin <> wrote:
Hi Tom:

On 2014-05-01 17:33+0100 Thomas Marsh wrote:

> Thanks for your message Alan. I could run "make xwin" but the subsequent
> commands failed for some reason.

Could you be more explicit about exactly what you did, and the error
messages that were generated?  I was careful to verify the commands I
suggested so those suggested C and Python tests work for me, and I am
quite surprised they do not work for you.

> Note however that I am able to run the
> Python version of plplot successfully already. I am not sure that what you
> describe is quite it. Does the example program exit before you exit the
> plot? (so that you could e.g type "ls" in the terminal from which you ran
> the example program, etc.) My guess is no. The equivalent in PGPLOT is the
> /xwindow device where it asks you to "hit <cr> for the next page:" and once
> you do this, the plot disappears and program execution continues (exiting
> if there is nothing left to do). The /xserve device does not produce the
> "hit <cr>" message but the program continues executing and the plot
> persists. The equivalent with plplot would be that the plot appears, the
> program exits but the plot still exists. As I understand /xserve, an
> independent server is created which carries on running even after the
> program that created it has exited.  This for example allows you to run
> another script and write a new plot into the plot window, or if you want
> open and write to a new window (by specifying "2/xserve", "3/xserve" etc).
> Here is the minimal Python example of where it differs relative to PGPLOT's
> /xserve:
> plsdev("xwin")
> plinit()
> plspause(False)
> plend()
> [rest of code]
> This continues executing rest code, but no plot is produced. If I do
> instead:
> plsdev("xwin")
> plinit()
> plend()
> a plot is produced, but has to explicitly exited before program execution
> resumes.

Thanks for this clarification of your needs.  In answer to your
specific question above, the example program does not exit before you
exit the plot, but I suggest you verify that yourself by running the
exact C and Python tests I recommended (i.e., follow up on why you
could not reproduce those simple test cases) to make absolutely sure
we are talking about the same things.

Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (; the Time
Ephemerides project (; PLplot scientific plotting
software package (; the libLASi project
(; the Loads of Linux Links project (;
and the Linux Brochure Project (

Linux-powered Science