matplotlib-0.87.7 Build Failure

If that shed additional light, again flush the build and

    >> install dirs, and try setting VERBOSE=True in setup.py before
    >> doing a clean install. The VERBOSE setting will generate lots
    >> of extra output and may help indicate where the segfault is
    >> occurring

    > No extra messages indicating any problems.

    > I did discover that there were two pkgconfig/
    > directories. I moved the few newer *.pc files from
    > /usr/local/lib/pkgconfig/ to /usr/lib/pkgconfig/, removed
    > the now empty directory, and rebuilt/installed from the
    > source tarball.

    > No joy. It still segfaults when I try to 'show()' the
    > plot.

If you recompiled cleanly (ie removed the build subdir) with
VERBOSE=True as instructed, you should be getting tons and tons of
output whenever you run a script (eg can you run simple_plot.py?). If
you are not getting the output, you are probably not running the
matplotlib you think you are. If you do get the output, post it along
with the script and the command line. Also, try running with
different backends, eg, PS, Agg. DO both segfault?

JDH

If you recompiled cleanly (ie removed the build subdir) with VERBOSE=True
as instructed, you should be getting tons and tons of output whenever you
run a script (eg can you run simple_plot.py?).

John,

   I was looking for verbose output during the build rather than when the
script ran. Now I'm on the same page as you are.

If you do get the output, post it along with the script and the command
line. Also, try running with different backends, eg, PS, Agg. DO both
segfault?

   simple_plot.py and the output (matplot.log) are attached. It is when the
show() command is run that the problem appears.

  How do I specify the backend for a run of the script?

Thanks,

Rich

···

On Thu, 11 Jan 2007, John Hunter wrote:

--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863