You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(14) |
Jun
(1) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(16) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(13) |
Feb
(22) |
Mar
(7) |
Apr
(8) |
May
(8) |
Jun
(11) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(31) |
Nov
(23) |
Dec
(3) |
2002 |
Jan
(1) |
Feb
(17) |
Mar
(10) |
Apr
(3) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
(11) |
Oct
(5) |
Nov
(21) |
Dec
(20) |
2003 |
Jan
(27) |
Feb
(13) |
Mar
(20) |
Apr
(11) |
May
(12) |
Jun
(7) |
Jul
(16) |
Aug
(21) |
Sep
(9) |
Oct
(28) |
Nov
(24) |
Dec
(30) |
2004 |
Jan
(31) |
Feb
(5) |
Mar
|
Apr
(8) |
May
(12) |
Jun
(7) |
Jul
(13) |
Aug
(12) |
Sep
(2) |
Oct
(14) |
Nov
(42) |
Dec
(14) |
2005 |
Jan
|
Feb
|
Mar
(20) |
Apr
(17) |
May
(9) |
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(17) |
Oct
(14) |
Nov
(9) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
(13) |
Apr
(2) |
May
(46) |
Jun
(2) |
Jul
(20) |
Aug
(26) |
Sep
(31) |
Oct
(5) |
Nov
(9) |
Dec
(13) |
2007 |
Jan
(24) |
Feb
(22) |
Mar
(13) |
Apr
(25) |
May
(25) |
Jun
(9) |
Jul
(20) |
Aug
(9) |
Sep
(26) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
2008 |
Jan
(92) |
Feb
(35) |
Mar
(39) |
Apr
(15) |
May
|
Jun
|
Jul
(18) |
Aug
(5) |
Sep
(5) |
Oct
(7) |
Nov
(10) |
Dec
(27) |
2009 |
Jan
(35) |
Feb
(34) |
Mar
(13) |
Apr
(9) |
May
(18) |
Jun
(9) |
Jul
(15) |
Aug
(13) |
Sep
(64) |
Oct
(7) |
Nov
(43) |
Dec
|
2010 |
Jan
(75) |
Feb
(22) |
Mar
(44) |
Apr
(34) |
May
(47) |
Jun
(77) |
Jul
(28) |
Aug
(7) |
Sep
(45) |
Oct
(1) |
Nov
(19) |
Dec
(7) |
2011 |
Jan
(14) |
Feb
|
Mar
(6) |
Apr
(12) |
May
(19) |
Jun
(3) |
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(21) |
Nov
(11) |
Dec
(4) |
2012 |
Jan
(2) |
Feb
(9) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(5) |
Oct
(1) |
Nov
(18) |
Dec
(2) |
2013 |
Jan
(15) |
Feb
(16) |
Mar
(8) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(17) |
Aug
(3) |
Sep
(17) |
Oct
(43) |
Nov
(25) |
Dec
(9) |
2014 |
Jan
(4) |
Feb
(8) |
Mar
(20) |
Apr
(14) |
May
(49) |
Jun
(1) |
Jul
|
Aug
(18) |
Sep
(2) |
Oct
(1) |
Nov
(22) |
Dec
(3) |
2015 |
Jan
(41) |
Feb
(2) |
Mar
(34) |
Apr
(30) |
May
(14) |
Jun
(17) |
Jul
(29) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(7) |
Dec
(4) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(25) |
Oct
(9) |
Nov
(14) |
Dec
(13) |
2017 |
Jan
(11) |
Feb
(8) |
Mar
(12) |
Apr
(4) |
May
(25) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
(10) |
Oct
(25) |
Nov
|
Dec
(6) |
2018 |
Jan
(18) |
Feb
(6) |
Mar
(6) |
Apr
(1) |
May
(7) |
Jun
(13) |
Jul
(8) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(17) |
Dec
(3) |
2019 |
Jan
(11) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
(1) |
Jun
(2) |
Jul
(8) |
Aug
(4) |
Sep
(32) |
Oct
(51) |
Nov
(1) |
Dec
(9) |
2020 |
Jan
(9) |
Feb
(6) |
Mar
|
Apr
|
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
|
2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Oliver B. <ol...@fi...> - 2008-01-12 16:52:28
|
Hello, I recently found the plplot-library and yesterday had started to explore it. It's really nice to use it. But btw, during my first experiments I found that it crashes wif not used in the correct way (for example changing two functions in order). Would be fine to fix such things. I also found some bugs on displaying data, when rotated. Would be fine when these things could be bugfixed. When I encounter errors, at least during this exploration stage, I save the c-code as well as the example-results. When I hav a couple of them I may send them to the developers or to a bugreporting tool, if there is one in use. For now I want to say that it's a fine library even in the presence of these problems. In the archive I found someone who wrote that he wants to write an OCaml-binding for plplot. That's fine. I had the same thing in mind, when looking at impressive the example-page of plplot. :-) But I also will be patient on the results ;-) Ciao, Oliver Bandel |
From: Antonio, F. Di N. <ant...@gm...> - 2008-01-10 23:35:08
|
On my winxp system, cmake error messages disappeared when switching from cmake 2.4.6 to cmake 2.4.7. Now I can compile plplot smoothly :-) 2008/1/10, Antonio, Fabio Di Narzo <ant...@gm...>: > Hi all. > Are there somewhere precompiled binaries of plplot for use with MinGW? > > This is for getting a fast test of my linux experiments with plplot > under win32. Unfortunatly, on my mingw setup, the CMake system doesn't > work out of the box (some CMake syntax error messages are given during > configure, no makefiles are produced), so I was hoping if someone can > free me from the hassle of compiling plplot from sources... > > Bests, > Antonio. > -- > Antonio, Fabio Di Narzo > Ph.D. student at > Department of Statistical Sciences > University of Bologna, Italy > -- Antonio, Fabio Di Narzo Ph.D. student at Department of Statistical Sciences University of Bologna, Italy |
From: Alan W. I. <ir...@be...> - 2008-01-10 17:53:15
|
On 2008-01-10 12:28+0100 Antonio, Fabio Di Narzo wrote: > Hi all. > I'm trying to use plplot for drawing png images. How can I specify the > image size (width and height)? Is there some common method for other > file/screen devices? > > I currently use the following skeleton code for my drawings: > plsdev("png"); > plsfnam("tmp.png"); > plinit(); > ... > plend(); Your primary question has already been answered by Werner, but I also want to encourage you to use command-line options rather than hard coding devices, filenames, and geometries. Thus, I would advise replacing the plsdev and plsfnam commands above with (void) plparseopts(&argc, argv, PL_PARSE_FULL); Then run your application like this: ./myplplot_application -dev png -o tmp.png -geometry 800x600 If you want to see the equivalent PostScript results, then use ./myplplot_application -dev psc -o tmp.ps To find all command-line options available to you use ./myplplot_application -h 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ |
From: Antonio, F. Di N. <ant...@gm...> - 2008-01-10 17:04:46
|
Hi all. Are there somewhere precompiled binaries of plplot for use with MinGW? This is for getting a fast test of my linux experiments with plplot under win32. Unfortunatly, on my mingw setup, the CMake system doesn't work out of the box (some CMake syntax error messages are given during configure, no makefiles are produced), so I was hoping if someone can free me from the hassle of compiling plplot from sources... Bests, Antonio. -- Antonio, Fabio Di Narzo Ph.D. student at Department of Statistical Sciences University of Bologna, Italy |
From: Antonio, F. Di N. <ant...@gm...> - 2008-01-10 12:56:13
|
Tnx! 2008/1/10, Werner Smekal <sm...@ia...>: > Hi, > > you need to use the geometry option. Within your program you need to > call the plsetopt function: http://plplot.sourceforge.net/docbook-manual/plplot-html-5.8.0/plsetopt.html > . > > so before plinit(); something like > > plsetopt( "-geometry", "1024x800" ); > > or something like that. > > Regards, > Werner > > > On 10.01.2008, at 12:28, Antonio, Fabio Di Narzo wrote: > > > Hi all. > > I'm trying to use plplot for drawing png images. How can I specify the > > image size (width and height)? Is there some common method for other > > file/screen devices? > > > > I currently use the following skeleton code for my drawings: > > plsdev("png"); > > plsfnam("tmp.png"); > > plinit(); > > ... > > plend(); > > > > Bests, > > Antonio, Fabio Di Narzo. > > -- > > Antonio, Fabio Di Narzo > > Ph.D. student at > > Department of Statistical Sciences > > University of Bologna, Italy > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > _______________________________________________ > > Plplot-general mailing list > > Plp...@li... > > https://lists.sourceforge.net/lists/listinfo/plplot-general > > -- > Dr. Werner Smekal > Institut fuer Allgemeine Physik > Technische Universitaet Wien > Wiedner Hauptstr 8-10 > A-1040 Wien > Austria > > email: sm...@ia... > web: http://www.iap.tuwien.ac.at/~smekal > phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory) > fax: +43-(0)1-58801-13499 > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general > |
From: Werner S. <sm...@ia...> - 2008-01-10 12:28:37
|
Hi, you need to use the geometry option. Within your program you need to call the plsetopt function: http://plplot.sourceforge.net/docbook-manual/plplot-html-5.8.0/plsetopt.html . so before plinit(); something like plsetopt( "-geometry", "1024x800" ); or something like that. Regards, Werner On 10.01.2008, at 12:28, Antonio, Fabio Di Narzo wrote: > Hi all. > I'm trying to use plplot for drawing png images. How can I specify the > image size (width and height)? Is there some common method for other > file/screen devices? > > I currently use the following skeleton code for my drawings: > plsdev("png"); > plsfnam("tmp.png"); > plinit(); > ... > plend(); > > Bests, > Antonio, Fabio Di Narzo. > -- > Antonio, Fabio Di Narzo > Ph.D. student at > Department of Statistical Sciences > University of Bologna, Italy > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general -- Dr. Werner Smekal Institut fuer Allgemeine Physik Technische Universitaet Wien Wiedner Hauptstr 8-10 A-1040 Wien Austria email: sm...@ia... web: http://www.iap.tuwien.ac.at/~smekal phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory) fax: +43-(0)1-58801-13499 |
From: Antonio, F. Di N. <ant...@gm...> - 2008-01-10 11:28:03
|
Hi all. I'm trying to use plplot for drawing png images. How can I specify the image size (width and height)? Is there some common method for other file/screen devices? I currently use the following skeleton code for my drawings: plsdev("png"); plsfnam("tmp.png"); plinit(); ... plend(); Bests, Antonio, Fabio Di Narzo. -- Antonio, Fabio Di Narzo Ph.D. student at Department of Statistical Sciences University of Bologna, Italy |
From: Hezekiah M. C. <hc...@at...> - 2007-12-12 18:48:38
|
On 12/11/07, Andrew Ross <and...@us...> wrote: > > Dear Hezekiah, > > It is great that you are working on plplot. We always welcome new > bindings. > > I must admit that I am have minimal experience with OCaml, but I thought > I would try it out. It built fine, but I'm unsure how to run the > example. Perhaps you could include some details? > > At some stage it would be good to integrate OCaml bindings into the > main plplot source. It sounds as if it would be good for you to discuss > with the author of the previous swig-based bindings which approach is > better and to combine efforts to work on the better approach. > > In general our approach has been to develop bindings which can be > generated automatically wherever possible. This minimises the work for > the core developers whenever adding new functionality and generally > provides a more robust and consistent approach. We already use swig for > the java and python bindings so there is some appeal in using this for > OCaml too. What are the advantages of camlidl over swig in this respect? > > To be integrated within plplot the bindings will have to be built using > CMake. If you have a working make file though the core developers are > likely to be able to help you with this, so don't let this put you off. > > Do keep working on this. > > Regards > > Andrew > Andrew, Thank you for the positive feedback. I am quite happy to hear that it actually builds for someone else! For the included example, the following should work to compile it to a bytecode executable: $ ocamlfind ocamlc -package plplot -linkpkg -o x11 x11.ml That is assuming you have compiled and installed the plplot bindings using make libinstall. If not, $ ocamlc -I ../ plplot.cma -o x11 x11.ml should work once the library is built, if you run that from the examples/ directory. I do intend to get in touch with the author of the SWIG-based bindings, but he has indicated previously on the OCaml mailing list that he will not have time to maintain them. My main reasons for using camlidl over SWIG are: a) I have also used SWIG to create HDF4 library bindings for OCaml, so I have some experience with it b) The process is relatively easy - I take a slightly modified plplot.h file, and preprocess it with a script I wrote. The output feeds in to camlidl which generates the binding code. This is quite similar, as I understand it, to how a SWIG binding would work. However... c) camlidl seems to produce much more lightweight bindings than SWIG. Looking through the existing SWIG-based OCaml bindings there are a large number of extra type wrappers which are not needed when using camlidl. There may be ways around this in SWIG which I do not know about. With that said, I am quite open to suggestions. The binding code I announced was the result of ~3 evenings of work, so it was not a huge effort thanks to (relative) ease of using OCaml's C interface. I would be happy to bring this in to the main plplot source tree and maintain it. I still have several things which need to be documented, such as callbacks - which are available for (I think) most of the functions which use them, but they are setup differently. Should the rest of this discussion continue on plplot-devel? Thank you again for the feedback. -- Hezekiah M. Carty Graduate Research Assistant University of Maryland Department of Atmospheric and Oceanic Science |
From: Andrew R. <and...@us...> - 2007-12-11 16:38:03
|
Dear Hezekiah, It is great that you are working on plplot. We always welcome new bindings. I must admit that I am have minimal experience with OCaml, but I thought I would try it out. It built fine, but I'm unsure how to run the example. Perhaps you could include some details? At some stage it would be good to integrate OCaml bindings into the main plplot source. It sounds as if it would be good for you to discuss with the author of the previous swig-based bindings which approach is better and to combine efforts to work on the better approach. In general our approach has been to develop bindings which can be generated automatically wherever possible. This minimises the work for the core developers whenever adding new functionality and generally provides a more robust and consistent approach. We already use swig for the java and python bindings so there is some appeal in using this for OCaml too. What are the advantages of camlidl over swig in this respect? To be integrated within plplot the bindings will have to be built using CMake. If you have a working make file though the core developers are likely to be able to help you with this, so don't let this put you off. Do keep working on this. Regards Andrew On Mon, Dec 10, 2007 at 03:00:35PM -0500, Hezekiah M. Carty wrote: > I would like to announce the availability of some reasonably complete > OCaml bindings for the PLplot library. There are still a few > functions missing, but the majority of the library is covered. > > The code can be downloaded from: > http://code.google.com/p/ocaml-plplot/ > > Requirements: > - OCaml (tested with 3.10.0, should work on older versions?) > - PLplot version 5.7.x or 5.8.x - tested with 5.7.3 through 5.8.0 > - camlidl > - findlib > > The license is the same as PLplot (LGPLv2+). > > This code has been developed on a 32bit CentOS 5 system, using godi > for the OCaml installation. I would be happy to hear about any > successes or failures on other systems. > > There is currently only one example included, which corresponds to > example 11 on the PLplot website. The PLplot documentation is a good > reference as this binding is very close to the C library. There are > some OCaml specific items though, so feel free to ask if you have > questions or problems. > > Enjoy! > > Note: > These are separate from previously announced PLplot bindings [1] - > those used SWIG to generate the interface, while this set of bindings > uses camlidl. These bindings are also somewhat more complete. > > [1] - http://vityok.org.ua/cgi-bin/odd.cgi/Ocaml-plplot > > -- > Hezekiah M. Carty > Graduate Research Assistant > University of Maryland > Department of Atmospheric and Oceanic Science > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general > |
From: Hezekiah M. C. <hc...@at...> - 2007-12-10 20:08:08
|
I would like to announce the availability of some reasonably complete OCaml bindings for the PLplot library. There are still a few functions missing, but the majority of the library is covered. The code can be downloaded from: http://code.google.com/p/ocaml-plplot/ Requirements: - OCaml (tested with 3.10.0, should work on older versions?) - PLplot version 5.7.x or 5.8.x - tested with 5.7.3 through 5.8.0 - camlidl - findlib The license is the same as PLplot (LGPLv2+). This code has been developed on a 32bit CentOS 5 system, using godi for the OCaml installation. I would be happy to hear about any successes or failures on other systems. There is currently only one example included, which corresponds to example 11 on the PLplot website. The PLplot documentation is a good reference as this binding is very close to the C library. There are some OCaml specific items though, so feel free to ask if you have questions or problems. Enjoy! Note: These are separate from previously announced PLplot bindings [1] - those used SWIG to generate the interface, while this set of bindings uses camlidl. These bindings are also somewhat more complete. [1] - http://vityok.org.ua/cgi-bin/odd.cgi/Ocaml-plplot -- Hezekiah M. Carty Graduate Research Assistant University of Maryland Department of Atmospheric and Oceanic Science |
From: Hazen B. <hba...@ma...> - 2007-11-18 21:00:32
|
Hello, The 5.8.0 stable release of PLplot is now available. This release contains a number of minor improvements since 5.8.0-RC1, most notably improved Cygwin support. Development releases in the 5.9.x series will be available in the coming months and the next stable release will be 5.10.0. As always, (1) Please refer to our wiki for the latest build and install instructions (http://www.miscdebris.net/plplot_wiki/index.php? title=Main_Page) and (2) Let us know of any problems / bugs that you run across while installing / using PLplot. best, -Hazen |
From: Arjen M. <arj...@wl...> - 2007-11-06 08:50:25
|
vasant j wrote: >Hi all, > > I am new to PLPLOT...I have installed the library....I >want to compile one example(x01c.c) program..... > >i did this...... > >gcc x01c.c -c x01c plplot-config --cflags --libs > >but it is showing error as > >undefined --cflags&--libs > >Send me one very simple program to print X & Y axes on plplot and how >to compile the program !! > >Kindly reply to this as soon as possible. > > > Hello Vasant, you made a small error in the command: gcc -o x01c x01c.c `plplot-config --cflags --libs` Note: "-c" is for compiling the source files only "-o name" names the output file, in this case the executable You need backticks (`) around the plplot-config, as the results from that command are substituted then. Regards, Arjen |
From: vasant j <vas...@gm...> - 2007-11-06 08:02:06
|
Hi all, I am new to PLPLOT...I have installed the library....I want to compile one example(x01c.c) program..... i did this...... gcc x01c.c -c x01c plplot-config --cflags --libs but it is showing error as undefined --cflags&--libs Send me one very simple program to print X & Y axes on plplot and how to compile the program !! Kindly reply to this as soon as possible. Regards, vasant |
From: sriram s. <rs...@ya...> - 2007-11-05 10:58:33
|
Hello, I have been having trouble building the static plplot libraries. Here is my system configuration: % Linux 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:59:08 EDT 2007 i686 i686 i386 GNU/Linux I untarred plplot-5.8.0-RC1.tar.gz. I then created a build directory build_dir in the directory plplot-5.8.0-RC1. In the build directory, I executed these commands (assuming that this is the right way to build the shared libraries): % cmake -DCMAKE_INSTALL_PREFIX=/n/asado/da/bioinfo/Software/ -DCMAKE_VERBOSE_MAKEFILE=ON -DBUILD_SHARED_LIBS=OFF .. >& cmake.out % make >& make.out The make procedure generates some errors. I have attached the files cmake.out and the last 30 lines of make.out. Installation works fine while building shared libraries (I remove the DBUILD_SHARED_LIBS=OFF flag ) and I can successfully link against libplplotd.so from a test C program. I initially tried to install the plplot-5.7.4 libraries. There again, I succeeded in installing the shared libraries and I could link against these libraries. Installation of the static libraries is also successful but there are errors when the test program is linked against these libraries. Thanks for your time, Sriram __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Alan W. I. <ir...@be...> - 2007-10-22 02:07:58
|
On 2007-10-21 16:24-0400 Hazen Babcock wrote: > > Hello, > > 5.8.0-RC1, our test release for the 5.8.0 stable release is now > available for download. Assuming that all is well with this release > then the official 5.8.0 stable release should be available in about > two weeks. Changes from the 5.7.4 release include updating the Octave > bindings to be compatible with Octave 2.9, adjusting the Fortran95 > bindings to work with a wider array of Fortran95 compilers and fixing > a number of bugs in the "3D" text routines plmtex3 and plptex3 (see > example 28). > > As always, (1) Please refer to our wiki for the latest build and > install instructions (http://www.miscdebris.net/plplot_wiki/index.php? > title=Main_Page) and (2) Let us know of any problems / bugs that you > run across while installing / using PLplot. Hi Hazen: I just built and tested 5.8.0-RC1 with just one (known) problem on a Debian oldstable (sarge) system with a specially built recent pango/cairo stack. The exact cmake command line was cmake -DCMAKE_INSTALL_PREFIX=/home/software/plplot_cvs/installcmake \ -DCMAKE_VERBOSE_MAKEFILE=ON -DENABLE_java=OFF -DENABLE_ada=ON \ -DBUILD_TEST=ON -DHAVE_NUMPY=OFF ../plplot_cmake >& cmake.out I turned off java because oldstable does not have a good free java that works with PLplot (free java versions of later Debian versions are fine). I also turned -DHAVE_NUMPY=OFF because I have python/numeric installed on oldstable rather than python/numpy. The installed examples seem fine for 5.8.0-RC1. A run of plplot-test.sh in the installed examples directory after the installed examples were built with the "make" command gave good results for the default psc device. Here are the ctest results: Start processing tests Test project /home/software/plplot_cvs/HEAD/build_dir 1/ 10 Testing examples_c Passed 2/ 10 Testing examples_cxx Passed 3/ 10 Testing examples_f77 Passed 4/ 10 Testing examples_octave Passed 5/ 10 Testing examples_python Passed 6/ 10 Testing examples_tcl Passed 7/ 10 Testing examples_ada Passed 8/ 10 Testing examples_psttfc ***Failed 9/ 10 Testing examples_png Passed 10/ 10 Testing examples_svg Passed 90% tests passed, 1 tests failed out of 10 The following tests FAILED: 8 - examples_psttfc (Failed) Errors while running CTest In the above, the f95 interface to PLplot was not tested because oldstable does not have gfortran. The examples_psttfc failure is a known problem for my particular setup (the special pango/cairo stack and svn version of libLASi) that apparently does not show up for other systems. Debian oldstable is pretty old, and I have some special libraries on top of that already special situation so I strongly encourage the rest of our users with access to modern Linux, Unix, Mac OS X, and Windows to give us reports (both good and bad) on our 5.8.0 release candidate to insure we have a forthcoming 5.8.0 stable release that works on as many popular platforms as possible. N.B. if there are any errors, please give the exact cmake command you used, and the _complete_ cmake and make command output (i.e, send to the list the compressed cmake.out and make.out files generated by cmake -Dwhatever_cmake_options ../path/to/sourcetree >& cmake.out make >& make.out .) Experience shows that if you give incomplete output for just where the error message occurs, then that is often not sufficient to debug the problem since many aspects of the PLplot configuration (with cmake) and build (with make) are interrelated. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ |
From: Hazen B. <hba...@ma...> - 2007-10-21 20:27:09
|
Hello, 5.8.0-RC1, our test release for the 5.8.0 stable release is now available for download. Assuming that all is well with this release then the official 5.8.0 stable release should be available in about two weeks. Changes from the 5.7.4 release include updating the Octave bindings to be compatible with Octave 2.9, adjusting the Fortran95 bindings to work with a wider array of Fortran95 compilers and fixing a number of bugs in the "3D" text routines plmtex3 and plptex3 (see example 28). As always, (1) Please refer to our wiki for the latest build and install instructions (http://www.miscdebris.net/plplot_wiki/index.php? title=Main_Page) and (2) Let us know of any problems / bugs that you run across while installing / using PLplot. best, -Hazen |
From: Charles P. <cwp...@bu...> - 2007-10-03 12:36:34
|
Thank you all :) With your feedback I have been able to get my application working quite well! --Chad On 9/18/07, Maurice LeBrun <mj...@br...> wrote: > > Charles Parker writes: > > Hello plplot community :^) > > > > I have two questions w/ regards to the functionality of the plplot C++ > > bindings. > > > > First, is it possible to plot single pixels in scatter plot (plpoin)? > I've > > tried using a lot of the different symbols and changing the size of > those > > symbols (with plssym), but I can't seem to find a combination that will > just > > turn on a single pixel for each data point I plot. > > There is a trick that works fine for the xwin driver. But the "points" > vanish > for e.g. the ps driver, so YMMV. From plysm.c -- > > > /*--------------------------------------------------------------------------*\ > * void plpoin() > * > * Plots array y against x for n points using ASCII code "code". > * > * code=-1 means try to just draw a point. Right now it's just a move and > * a draw at the same place. Not ideal, since a sufficiently intelligent > * output device may optimize it away, or there may be faster ways of > * doing it. This is OK for now, though, and offers a 4X speedup over > * drawing a Hershey font "point" (which is actually diamond shaped and > * therefore takes 4 strokes to draw). > > \*--------------------------------------------------------------------------*/ > > void > c_plpoin(PLINT n, PLFLT *x, PLFLT *y, PLINT code) > > > Second, I'm going to be plotting about 5000 data points or so, the > problem > > is that the way my data are structured, the points I need to plot are > not > > stored sequentially in memory. I have data with about 15 parameters per > > point, and I only want to plot points (the x and y are two of the > > parameters) that satisfy some filtering criteria. Am I better off simply > > taking the memory and performance hit to create an additional data > structure > > in which these data are sequential? Or can I simply call plpoin to plot > each > > individual point? In the latter case I would loop through the data only > once > > and plot points as I found them, whereas in the former there is the > extra > > overhead of creating the data structure and copying the data before I > can > > plot it. > > Calling plpoin for each point separately should be fine. > > -- > Maurice LeBrun > |
From: Maurice L. <mj...@br...> - 2007-09-18 08:25:38
|
Charles Parker writes: > Hello plplot community :^) > > I have two questions w/ regards to the functionality of the plplot C++ > bindings. > > First, is it possible to plot single pixels in scatter plot (plpoin)? I've > tried using a lot of the different symbols and changing the size of those > symbols (with plssym), but I can't seem to find a combination that will just > turn on a single pixel for each data point I plot. There is a trick that works fine for the xwin driver. But the "points" vanish for e.g. the ps driver, so YMMV. From plysm.c -- /*--------------------------------------------------------------------------*\ * void plpoin() * * Plots array y against x for n points using ASCII code "code". * * code=-1 means try to just draw a point. Right now it's just a move and * a draw at the same place. Not ideal, since a sufficiently intelligent * output device may optimize it away, or there may be faster ways of * doing it. This is OK for now, though, and offers a 4X speedup over * drawing a Hershey font "point" (which is actually diamond shaped and * therefore takes 4 strokes to draw). \*--------------------------------------------------------------------------*/ void c_plpoin(PLINT n, PLFLT *x, PLFLT *y, PLINT code) > Second, I'm going to be plotting about 5000 data points or so, the problem > is that the way my data are structured, the points I need to plot are not > stored sequentially in memory. I have data with about 15 parameters per > point, and I only want to plot points (the x and y are two of the > parameters) that satisfy some filtering criteria. Am I better off simply > taking the memory and performance hit to create an additional data structure > in which these data are sequential? Or can I simply call plpoin to plot each > individual point? In the latter case I would loop through the data only once > and plot points as I found them, whereas in the former there is the extra > overhead of creating the data structure and copying the data before I can > plot it. Calling plpoin for each point separately should be fine. -- Maurice LeBrun |
From: Arjen M. <arj...@wl...> - 2007-09-18 06:29:40
|
Alan W. Irwin wrote: > > >>Second, I'm going to be plotting about 5000 data points or so, the problem >>is that the way my data are structured, the points I need to plot are not >>stored sequentially in memory. I have data with about 15 parameters per >>point, and I only want to plot points (the x and y are two of the >>parameters) that satisfy some filtering criteria. Am I better off simply >>taking the memory and performance hit to create an additional data structure >>in which these data are sequential? Or can I simply call plpoin to plot each >>individual point? In the latter case I would loop through the data only once >>and plot points as I found them, whereas in the former there is the extra >>overhead of creating the data structure and copying the data before I can >>plot it. >> >> > >I think the speed for unordered access will depend on the size of your cache >and the degree of non-locality of reference. Taking data out of order may >actually make little difference at all. Regardless of that, I always >try as a general rule to use the simplest programming to prototype what I >want and optimize further (with the associated increased danger of >introducing bugs) only if really necessary. Anyhow, that is what I suggest >in the present case. > > I would like to support Alan's advice: first set up a prototype that follows the "natural" data structure that you have. Then if that seems too slow, measure the time spent in each function (use a profiler for that - do not "guess", we human beings are very bad at guessing which function will take all computational time) and try to decide from that how to change the algorithm. If stepping through the data set seems the dominant factor, then that is easy to tell: just replace the call to a PLplot function like plpoin() by a call to a dummy function with the same signature (plotting takes time too!) Regards, Arjen |
From: Alan W. I. <ir...@be...> - 2007-09-18 02:57:53
|
On 2007-09-17 20:24-0400 Charles Parker wrote: > Hello plplot community :^) Welcome to the list. > > I have two questions w/ regards to the functionality of the plplot C++ > bindings. > > First, is it possible to plot single pixels in scatter plot (plpoin)? I've > tried using a lot of the different symbols and changing the size of those > symbols (with plssym), but I can't seem to find a combination that will just > turn on a single pixel for each data point I plot. I have discovered recently that some devices (e.g., the pscairo device that is part of the new cairo device driver family) honor font hinting. One characteristic of font hinting is it aligns characters with the pixel grid. I don't know what happens for small characters, but I assume you would get an equal hit on 4 pixels or a hit on one pixel. Anyhow, try pscairo (from latest svn) and see whether it helps. When viewing the results you will have to turn off antialiasing in your PostScript viewer to see exactly which pixels have been painted. For devices that don't honor font hinting, world coordinates are not going to be aligned with pixel coordinates so more than one pixel will be involved when painting a dot at arbitrary x, y. However, from the known pixel range of your device, you should be able to do your own pixel alignment by carefully choosing plvpor values and world coordinates so the latter match integer pixel values. Then it is only a matter of taking the nearest integral value for the x and y positions to get consistent alignment on pixels. Under those circumstances, your tiny characters should always at least look the same, and may even correspond to painting a single pixel for the no antialiasing case. > > Second, I'm going to be plotting about 5000 data points or so, the problem > is that the way my data are structured, the points I need to plot are not > stored sequentially in memory. I have data with about 15 parameters per > point, and I only want to plot points (the x and y are two of the > parameters) that satisfy some filtering criteria. Am I better off simply > taking the memory and performance hit to create an additional data structure > in which these data are sequential? Or can I simply call plpoin to plot each > individual point? In the latter case I would loop through the data only once > and plot points as I found them, whereas in the former there is the extra > overhead of creating the data structure and copying the data before I can > plot it. I think the speed for unordered access will depend on the size of your cache and the degree of non-locality of reference. Taking data out of order may actually make little difference at all. Regardless of that, I always try as a general rule to use the simplest programming to prototype what I want and optimize further (with the associated increased danger of introducing bugs) only if really necessary. Anyhow, that is what I suggest in the present case. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ |
From: Charles P. <cwp...@bu...> - 2007-09-18 00:24:23
|
Hello plplot community :^) I have two questions w/ regards to the functionality of the plplot C++ bindings. First, is it possible to plot single pixels in scatter plot (plpoin)? I've tried using a lot of the different symbols and changing the size of those symbols (with plssym), but I can't seem to find a combination that will just turn on a single pixel for each data point I plot. Second, I'm going to be plotting about 5000 data points or so, the problem is that the way my data are structured, the points I need to plot are not stored sequentially in memory. I have data with about 15 parameters per point, and I only want to plot points (the x and y are two of the parameters) that satisfy some filtering criteria. Am I better off simply taking the memory and performance hit to create an additional data structure in which these data are sequential? Or can I simply call plpoin to plot each individual point? In the latter case I would loop through the data only once and plot points as I found them, whereas in the former there is the extra overhead of creating the data structure and copying the data before I can plot it. Any advice would be appreciated! Thanks, --Chad |
From: Alan W. I. <ir...@be...> - 2007-09-11 17:41:34
|
On 2007-09-11 09:51-0400 Scott Hall wrote: > [...]So I simply ignored the GD, TCL > and pdf issue by disabling them or not initializing them. However when I go > to test the examples I am still recieving linker errors. I tried this for > both a static and dynamic build and the same errors are produced. Please > see the error message below. [...] > ----- > ----- DYNAMIC BUILD EXAMPLES RESULTS > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > hall000s@pillbox(/tmp/examples) - 290: make > target=`echo all`; \ > list='c c++ f77 f95 tk java'; for subdir in $list; do \ > if test -d "$subdir"; then \ > echo "Making $target in $subdir"; \ > (cd $subdir && make $target); \ > fi; \ > done > Making all in c > make[1]: Entering directory `/tmp/examples/c' > /usw/ude/SunOS/bin/gcc x01c.c -o x01c -Wl,-rpath > -Wl,/home/hall000s/SunOS/plplot_dyn/lib > `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig pkg-config > --cflags --libs plplotd` > ld: fatal: option -dn and -P are incompatible > ld: fatal: Flags processing errors > collect2: ld returned 1 exit status > make[1]: *** [x01c] Error 1 > make[1]: Leaving directory `/tmp/examples/c' Above I am emphasizing information from your solaris build of C examples using the dynamic libraries because that is the simplest case I am familiar with on Linux. What are the actual results of running PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig \ pkg-config --cflags --libs plplotd ? That should be the same information that cmake has configured and installed in /home/hall000s/SunOS/plplot_dyn/lib/pkgconfig/plplotd.pc. Could you post that file (as an attachment) in your reply? A temporary workaround is to edit that file to get rid of the linker flags that solaris does not like. That should be enough to get you moving forward again, but the interesting question from my perspective is why plplotd.pc is configured incorrectly with wrong information in the solaris shared libraries case. cmake should simply copy what it does for applications in the build tree, and from your reports that build tree linking is working fine. Could you also send the complete make.out (as an attachment) from your dynamic build so I can compare the working solaris build in that case with the non-working one for the install tree? Thanks in advance for the additional requested information. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ |
From: Scott H. <smh...@gm...> - 2007-09-11 13:51:04
|
Alan thanks for the pointers with cmake. I added the :PATH or FILEPATH where applicable and that worked in successfully configuring everything. There were a few random problems but I was able to work my way around them by disabling certain features. For instance cmake could not find my GD library even though the path and file I provided was valid. During the actual make TCL created a compiler error and there was unreferenced symbol errors which occured in the pdf library. So I simply ignored the GD, TCL and pdf issue by disabling them or not initializing them. However when I go to test the examples I am still recieving linker errors. I tried this for both a static and dynamic build and the same errors are produced. Please see the error message below. --- --- STATIC BUILD EXAMPLE RESULTS ------------------------------------------------------------------------------------------------------------------------------ hall000s@pillbox(/tmp/examples) - 288: make target=`echo all`; \ list='c c++ f77 f95 tk java'; for subdir in $list; do \ if test -d "$subdir"; then \ echo "Making $target in $subdir"; \ (cd $subdir && make $target); \ fi; \ done Making all in c make[1]: Entering directory `/tmp/examples/c' /usw/ude/SunOS/bin/gcc x01c.c -o x01c -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_static/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_static/lib/pkgconfig pkg-config --cflags --libs plplotd` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01c] Error 1 make[1]: Leaving directory `/tmp/examples/c' Making all in c++ make[1]: Entering directory `/tmp/examples/c++' /usw/ude/SunOS/bin/c++ x01cc.cc -o x01cc -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_static/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_static/lib/pkgconfig pkg-config --cflags --libs plplotd-c++` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01cc] Error 1 make[1]: Leaving directory `/tmp/examples/c++' Making all in f77 make[1]: Entering directory `/tmp/examples/f77' /usw/ude/SunOS/bin/g95 x01f.f -o x01f -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_static/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_static/lib/pkgconfig pkg-config --cflags --libs plplotd-f77` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors make[1]: *** [x01f] Error 1 make[1]: Leaving directory `/tmp/examples/f77' Making all in f95 make[1]: Entering directory `/tmp/examples/f95' /usw/ude/SunOS/bin/g95 x01f.f90 -o x01f -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_static/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_static/lib/pkgconfig pkg-config --cflags --libs plplotd-f95` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors make[1]: *** [x01f] Error 1 make[1]: Leaving directory `/tmp/examples/f95' ----- ----- DYNAMIC BUILD EXAMPLES RESULTS ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ hall000s@pillbox(/tmp/examples) - 290: make target=`echo all`; \ list='c c++ f77 f95 tk java'; for subdir in $list; do \ if test -d "$subdir"; then \ echo "Making $target in $subdir"; \ (cd $subdir && make $target); \ fi; \ done Making all in c make[1]: Entering directory `/tmp/examples/c' /usw/ude/SunOS/bin/gcc x01c.c -o x01c -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_dyn/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig pkg-config --cflags --libs plplotd` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01c] Error 1 make[1]: Leaving directory `/tmp/examples/c' Making all in c++ make[1]: Entering directory `/tmp/examples/c++' /usw/ude/SunOS/bin/c++ x01cc.cc -o x01cc -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_dyn/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig pkg-config --cflags --libs plplotd-c++` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01cc] Error 1 make[1]: Leaving directory `/tmp/examples/c++' Making all in f77 make[1]: Entering directory `/tmp/examples/f77' /usw/ude/SunOS/bin/g95 x01f.f -o x01f -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_dyn/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig pkg-config --cflags --libs plplotd-f77` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors make[1]: *** [x01f] Error 1 make[1]: Leaving directory `/tmp/examples/f77' Making all in f95 make[1]: Entering directory `/tmp/examples/f95' /usw/ude/SunOS/bin/g95 x01f.f90 -o x01f -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_dyn/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_dyn/lib/pkgconfig pkg-config --cflags --libs plplotd-f95` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors make[1]: *** [x01f] Error 1 make[1]: Leaving directory `/tmp/examples/f95' Thanks again for your help. Scott On 9/8/07, Alan W. Irwin <ir...@be...> wrote: > > On 2007-09-08 13:21-0400 Scott Hall wrote: > > > I am running into a peculiar installation problem while trying to > install > > PLplot-5.7.4 on Solaris. I have been at this installation for quite > awhile > > and the problems I keep running into are strange and I am not sure how > to > > fix them. > > > So my next step was to start from scratch and gradually enable more > bindings > > and drivers. So I went back to cmake and ran this following command, > also I > > am trying to create a static build, this is a requirement of my > build. I am > > building this in a separate folder from the plplot source directory. > > > > cmake > -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ > > -DCMAKE_INSTALL_BINDIR=/home/hall000s/SunOS/plplot/bin > > \ > > -DCMAKE_INSTALL_DATADIR=/home/hall000s/SunOS/plplot/share \ > > -DCMAKE_INSTALL_EXEC_PREFIX=/home/hall000s/SunOS/plplot \ > > -DCMAKE_INSTALL_INCLUDEDIR=/home/hall000s/SunOS/plplot/include \ > > -DCMAKE_INSTALL_INFODIR=/home/hall000s/SunOS/plplot/share/info \ > > > > -DCMAKE_INSTALL_LIBDIR=/home/hall000s/SunOS/plplot/lib > \ > > -DCMAKE_INSTALL_MANDIR=/home/hall000s/SunOS/plplot/share/man \ > > > > -DDEFAULT_NO_DEVICES=ON > > \ > > > > -DDEFAULT_NO_BINDINGS=ON > > \ > > > > -DBUILD_SHARED_LIBS=OFF > > \ > > > > -DPKG_CONFIG_EXECUTABLE=/bin/pkg-config > > \ > > > > -DPLD_ps=ON > > \ > > ../plplot-5.7.4 > > > > When the above cmake command is executed it shows the following output. > > [...]Summary of CMake build system results for PLplot > > > > Install location variables which can be set by the user: > > CMAKE_INSTALL_PREFIX: > > CMAKE_INSTALL_EXEC_PREFIX > > CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR > > CMAKE_INSTALL_DATADIR > > CMAKE_INSTALL_LIBDIR > > CMAKE_INSTALL_INCLUDEDIR > > CMAKE_INSTALL_INFODIR > > CMAKE_INSTALL_MANDIR > > > > Derived install location variables: > > DATA_DIR /plplot5.7.4 > > LIB_DIR > > INCLUDE_DIR /plplot > > BIN_DIR CMAKE_INSTALL_BINDIR > > TCL_DIR /plplot5.7.4/tcl > > PYTHON_INSTDIR > > DRV_DIR /plplot5.7.4/driversd > > DOC_DIR /doc/plplot > > MAN_DIR > > INFO_DIR > > > > Other important CMake variables: > > > > CMAKE_SYSTEM_NAME: SunOS > > UNIX: 1 > > WIN32: > > APPLE: > > MSVC: (MSVC_VERSION: ) > > MINGW: > > MSYS: > > CYGWIN: > > BORLAND: > > WATCOM: > > > > SWIG_FOUND: FALSE > > PERL_FOUND: YES > > X11_FOUND: 1 > > > > CMAKE_BUILD_TYPE: > > CMAKE_C_COMPILER CMAKE_C_FLAGS: /usw/ude/SunOS/bin/gcc > > LIB_TAG: d > > > > ENABLE_DYNDRIVERS: OFF > > DEVICES_LIST: ps > > DRIVERS_LIST: ps > > > > Library options: > > BUILD_SHARED_LIBS: OFF PL_DOUBLE: ON > > > > Optional libraries: > > HAVE_QHULL: OFF WITH_CSA: ON > > HAVE_FREETYPE: HAVE_PTHREAD: > > HAVE_AGG: > > > > Language Bindings: > > ENABLE_f77: OFF ENABLE_f95: OFF > > ENABLE_cxx: OFF ENABLE_java: OFF > > ENABLE_python: OFF ENABLE_octave: OFF > > ENABLE_tcl: OFF ENABLE_itcl: OFF > > ENABLE_tk: OFF ENABLE_itk: OFF > > ENABLE_pdl: OFF ENABLE_wxwidgets: OFF > > ENABLE_gnome2: OFF ENABLE_pygcw: OFF > > ENABLE_ada: OFF > > > > Notice that it did not find my pkg-config executable even though the > path I > > gave it is correct. This occurs with some of the devices and bindings > as > > well. However if I was to use ccmake and enter the same paths that I am > > using for cmake I have success. Has anyone ran into any problems like > > this? I appreciate any help with this problem. > > I think you are running afoul of a CMake peculiarity (which apparently is > fixed in the CVS version of CMake which should get released in the future > as > the 2.6.x series). According to the documentation (which you can look at > with cmake --help-full |less) the -D options all have to be typed (e.g., > given > a type of BOOL, FILEPATH, PATH, STRING, or INTERNAL) > for cmake-2.4.x. However, there are exceptions to this rule which I > have discovered experimentally. For example, you don't have to specify > any type for the ON/OFF BOOL variables, and > -DCMAKE_INSTALL_PREFIX. However, > for other paths or filepaths you do have to specify PATH or FILEPATH. > > So try changing your above command to the following > > cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ > -DCMAKE_INSTALL_BINDIR:PATH=/home/hall000s/SunOS/plplot/bin \ > -DCMAKE_INSTALL_DATADIR:PATH=/home/hall000s/SunOS/plplot/share \ > -DCMAKE_INSTALL_EXEC_PREFIX:PATH=/home/hall000s/SunOS/plplot \ > -DCMAKE_INSTALL_INCLUDEDIR:PATH=/home/hall000s/SunOS/plplot/include \ > -DCMAKE_INSTALL_INFODIR:PATH=/home/hall000s/SunOS/plplot/share/info \ > -DCMAKE_INSTALL_LIBDIR:PATH=/home/hall000s/SunOS/plplot/lib \ > -DCMAKE_INSTALL_MANDIR:PATH=/home/hall000s/SunOS/plplot/share/man \ > -DDEFAULT_NO_DEVICES=ON \ > -DDEFAULT_NO_BINDINGS=ON \ > -DBUILD_SHARED_LIBS=OFF \ > -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config \ > -DPLD_ps=ON \ > ../plplot-5.7.4 > > You can check the cache file CMakeCache.txt, for any other variable types > you might need. > > N.B. While you are getting used to cmake, be sure to make a clean start > every time by running the above command in an empty build > directory. Also, > never use a source tree where cmake has been run by accident since that > convinces all future invocations of cmake to always use a build in the > source tree. To assure this is not a problem, use a freshly unpacked > source tree and then from then on always invoke cmake from a separate > build tree (as above). Finally, completely remove the install tree before > running cmake to make sure there is nothing stale there that will screw > up your installed examples test. > > Here is a further suggestion about the above invocation of cmake. Above, > you are specifying a lot of stuff that happens by default. If you drop > those unnnecessary options, then the above cmake command boils down to > > cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ > -DDEFAULT_NO_DEVICES=ON \ > -DDEFAULT_NO_BINDINGS=ON \ > -DBUILD_SHARED_LIBS=OFF \ > -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config \ > -DPLD_ps=ON \ > ../plplot-5.7.4 > > You can even drop -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config if /bin > is on your PATH. The reason for this simplification is > cmake/modules/FindPkgConfig.cmake uses the cmake "find_program" command to > find pkg-config, and that command does the right thing (i.e., checks for > programmes in all directories in the PATH by default). > > ccmake is useful to give you an idea of the annotated options, but it is > not > really necessary since those annotations also show up in the cache file, > CMakeCache.txt. Also, I personally find ccmake confusing since there is > always a question whether it is using stale cache file results or not. If > you always invoke cmake in an empty build tree, then by definition there > are > no stale cache problems. > > I think this is our first cmake build report on solaris so we are much > interested in your results and will help as much as we can. It appears > from > the rest of your message (not quoted) that you are running into troubles > with the installed examples test for a static build so it would be > interesting to see if those troubles extend to the shared build case as > well > (which is tested a lot more than the static build case). To do a shared > build, simply specify -DBUILD_SHARED_LIBS=ON, and also specify a separate > installation prefix to keep that shared install tree separate from your > desired static install tree. Also, I have to say that your approach of > simplifying the PLplot build as much as possible with no interfaces and no > device drivers other than ps is the right way to debug what is going on. > But > you do have to remember to always invoke cmake in an empty build tree to > avoid stale cache issues and also you should remove the install tree > before > invoking cmake to avoid stale installation files. > > Good luck and keep us posted how it goes. > > 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); PLplot scientific plotting > software > package (plplot.org); 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 > __________________________ > |
From: Alan W. I. <ir...@be...> - 2007-09-08 19:24:40
|
On 2007-09-08 13:21-0400 Scott Hall wrote: > I am running into a peculiar installation problem while trying to install > PLplot-5.7.4 on Solaris. I have been at this installation for quite awhile > and the problems I keep running into are strange and I am not sure how to > fix them. > So my next step was to start from scratch and gradually enable more bindings > and drivers. So I went back to cmake and ran this following command, also I > am trying to create a static build, this is a requirement of my build. I am > building this in a separate folder from the plplot source directory. > > cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ > -DCMAKE_INSTALL_BINDIR=/home/hall000s/SunOS/plplot/bin > \ > -DCMAKE_INSTALL_DATADIR=/home/hall000s/SunOS/plplot/share \ > -DCMAKE_INSTALL_EXEC_PREFIX=/home/hall000s/SunOS/plplot \ > -DCMAKE_INSTALL_INCLUDEDIR=/home/hall000s/SunOS/plplot/include \ > -DCMAKE_INSTALL_INFODIR=/home/hall000s/SunOS/plplot/share/info \ > > -DCMAKE_INSTALL_LIBDIR=/home/hall000s/SunOS/plplot/lib \ > -DCMAKE_INSTALL_MANDIR=/home/hall000s/SunOS/plplot/share/man \ > > -DDEFAULT_NO_DEVICES=ON > \ > > -DDEFAULT_NO_BINDINGS=ON > \ > > -DBUILD_SHARED_LIBS=OFF > \ > > -DPKG_CONFIG_EXECUTABLE=/bin/pkg-config > \ > > -DPLD_ps=ON > \ > ../plplot-5.7.4 > > When the above cmake command is executed it shows the following output. > [...]Summary of CMake build system results for PLplot > > Install location variables which can be set by the user: > CMAKE_INSTALL_PREFIX: > CMAKE_INSTALL_EXEC_PREFIX > CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR > CMAKE_INSTALL_DATADIR > CMAKE_INSTALL_LIBDIR > CMAKE_INSTALL_INCLUDEDIR > CMAKE_INSTALL_INFODIR > CMAKE_INSTALL_MANDIR > > Derived install location variables: > DATA_DIR /plplot5.7.4 > LIB_DIR > INCLUDE_DIR /plplot > BIN_DIR CMAKE_INSTALL_BINDIR > TCL_DIR /plplot5.7.4/tcl > PYTHON_INSTDIR > DRV_DIR /plplot5.7.4/driversd > DOC_DIR /doc/plplot > MAN_DIR > INFO_DIR > > Other important CMake variables: > > CMAKE_SYSTEM_NAME: SunOS > UNIX: 1 > WIN32: > APPLE: > MSVC: (MSVC_VERSION: ) > MINGW: > MSYS: > CYGWIN: > BORLAND: > WATCOM: > > SWIG_FOUND: FALSE > PERL_FOUND: YES > X11_FOUND: 1 > > CMAKE_BUILD_TYPE: > CMAKE_C_COMPILER CMAKE_C_FLAGS: /usw/ude/SunOS/bin/gcc > LIB_TAG: d > > ENABLE_DYNDRIVERS: OFF > DEVICES_LIST: ps > DRIVERS_LIST: ps > > Library options: > BUILD_SHARED_LIBS: OFF PL_DOUBLE: ON > > Optional libraries: > HAVE_QHULL: OFF WITH_CSA: ON > HAVE_FREETYPE: HAVE_PTHREAD: > HAVE_AGG: > > Language Bindings: > ENABLE_f77: OFF ENABLE_f95: OFF > ENABLE_cxx: OFF ENABLE_java: OFF > ENABLE_python: OFF ENABLE_octave: OFF > ENABLE_tcl: OFF ENABLE_itcl: OFF > ENABLE_tk: OFF ENABLE_itk: OFF > ENABLE_pdl: OFF ENABLE_wxwidgets: OFF > ENABLE_gnome2: OFF ENABLE_pygcw: OFF > ENABLE_ada: OFF > > Notice that it did not find my pkg-config executable even though the path I > gave it is correct. This occurs with some of the devices and bindings as > well. However if I was to use ccmake and enter the same paths that I am > using for cmake I have success. Has anyone ran into any problems like > this? I appreciate any help with this problem. I think you are running afoul of a CMake peculiarity (which apparently is fixed in the CVS version of CMake which should get released in the future as the 2.6.x series). According to the documentation (which you can look at with cmake --help-full |less) the -D options all have to be typed (e.g., given a type of BOOL, FILEPATH, PATH, STRING, or INTERNAL) for cmake-2.4.x. However, there are exceptions to this rule which I have discovered experimentally. For example, you don't have to specify any type for the ON/OFF BOOL variables, and -DCMAKE_INSTALL_PREFIX. However, for other paths or filepaths you do have to specify PATH or FILEPATH. So try changing your above command to the following cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ -DCMAKE_INSTALL_BINDIR:PATH=/home/hall000s/SunOS/plplot/bin \ -DCMAKE_INSTALL_DATADIR:PATH=/home/hall000s/SunOS/plplot/share \ -DCMAKE_INSTALL_EXEC_PREFIX:PATH=/home/hall000s/SunOS/plplot \ -DCMAKE_INSTALL_INCLUDEDIR:PATH=/home/hall000s/SunOS/plplot/include \ -DCMAKE_INSTALL_INFODIR:PATH=/home/hall000s/SunOS/plplot/share/info \ -DCMAKE_INSTALL_LIBDIR:PATH=/home/hall000s/SunOS/plplot/lib \ -DCMAKE_INSTALL_MANDIR:PATH=/home/hall000s/SunOS/plplot/share/man \ -DDEFAULT_NO_DEVICES=ON \ -DDEFAULT_NO_BINDINGS=ON \ -DBUILD_SHARED_LIBS=OFF \ -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config \ -DPLD_ps=ON \ ../plplot-5.7.4 You can check the cache file CMakeCache.txt, for any other variable types you might need. N.B. While you are getting used to cmake, be sure to make a clean start every time by running the above command in an empty build directory. Also, never use a source tree where cmake has been run by accident since that convinces all future invocations of cmake to always use a build in the source tree. To assure this is not a problem, use a freshly unpacked source tree and then from then on always invoke cmake from a separate build tree (as above). Finally, completely remove the install tree before running cmake to make sure there is nothing stale there that will screw up your installed examples test. Here is a further suggestion about the above invocation of cmake. Above, you are specifying a lot of stuff that happens by default. If you drop those unnnecessary options, then the above cmake command boils down to cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ -DDEFAULT_NO_DEVICES=ON \ -DDEFAULT_NO_BINDINGS=ON \ -DBUILD_SHARED_LIBS=OFF \ -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config \ -DPLD_ps=ON \ ../plplot-5.7.4 You can even drop -DPKG_CONFIG_EXECUTABLE:FILEPATH=/bin/pkg-config if /bin is on your PATH. The reason for this simplification is cmake/modules/FindPkgConfig.cmake uses the cmake "find_program" command to find pkg-config, and that command does the right thing (i.e., checks for programmes in all directories in the PATH by default). ccmake is useful to give you an idea of the annotated options, but it is not really necessary since those annotations also show up in the cache file, CMakeCache.txt. Also, I personally find ccmake confusing since there is always a question whether it is using stale cache file results or not. If you always invoke cmake in an empty build tree, then by definition there are no stale cache problems. I think this is our first cmake build report on solaris so we are much interested in your results and will help as much as we can. It appears from the rest of your message (not quoted) that you are running into troubles with the installed examples test for a static build so it would be interesting to see if those troubles extend to the shared build case as well (which is tested a lot more than the static build case). To do a shared build, simply specify -DBUILD_SHARED_LIBS=ON, and also specify a separate installation prefix to keep that shared install tree separate from your desired static install tree. Also, I have to say that your approach of simplifying the PLplot build as much as possible with no interfaces and no device drivers other than ps is the right way to debug what is going on. But you do have to remember to always invoke cmake in an empty build tree to avoid stale cache issues and also you should remove the install tree before invoking cmake to avoid stale installation files. Good luck and keep us posted how it goes. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ |
From: Scott H. <smh...@gm...> - 2007-09-08 17:21:16
|
I am running into a peculiar installation problem while trying to install PLplot-5.7.4 on Solaris. I have been at this installation for quite awhile and the problems I keep running into are strange and I am not sure how to fix them. I started my installation by basically installing everything I could via cmake, but cmake's configuration results indicated that it could not find libraries, include files, etc from the paths I gave it. The paths I gave cmake are correct. I was at a loss from that point so I decided to try my installation using ccmake. I used the same paths as I was using in cmake and everything was able to configure and then make correctly. However when I went to test PLplot (via the INSTALL post make instructions) I recieved some wierd linking errors. target=`echo all`; \ list='c c++ f77 f95 tk java'; for subdir in $list; do \ if test -d "$subdir"; then \ echo "Making $target in $subdir"; \ (cd $subdir && make $target); \ fi; \ done Making all in c make[1]: Entering directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/c' /usw/ude/SunOS/bin/gcc x01c.c -o x01c -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_ccmake/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_ccmake/lib/pkgconfig pkg-config --cflags --libs plplotd` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01c] Error 1 make[1]: Leaving directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/c' Making all in c++ make[1]: Entering directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/c++' /usw/ude/SunOS/bin/c++ x01cc.cc -o x01cc -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_ccmake/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_ccmake/lib/pkgconfig pkg-config --cflags --libs plplotd-c++` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors collect2: ld returned 1 exit status make[1]: *** [x01cc] Error 1 make[1]: Leaving directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/c++' Making all in f77 make[1]: Entering directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/f77' /usw/ude/SunOS/bin/g95 x01f.f -o x01f -Wl,-rpath -Wl,/home/hall000s/SunOS/plplot_ccmake/lib `PKG_CONFIG_PATH=/home/hall000s/SunOS/plplot_ccmake/lib/pkgconfig pkg-config --cflags --libs plplotd-f77` ld: fatal: option -dn and -P are incompatible ld: fatal: Flags processing errors make[1]: *** [x01f] Error 1 make[1]: Leaving directory `/home/hall000s/SunOS/plplot_ccmake/share/plplot5.7.4/examples/f77' So my next step was to start from scratch and gradually enable more bindings and drivers. So I went back to cmake and ran this following command, also I am trying to create a static build, this is a requirement of my build. I am building this in a separate folder from the plplot source directory. cmake -DCMAKE_INSTALL_PREFIX=/home/hall000s/SunOS/plplot \ -DCMAKE_INSTALL_BINDIR=/home/hall000s/SunOS/plplot/bin \ -DCMAKE_INSTALL_DATADIR=/home/hall000s/SunOS/plplot/share \ -DCMAKE_INSTALL_EXEC_PREFIX=/home/hall000s/SunOS/plplot \ -DCMAKE_INSTALL_INCLUDEDIR=/home/hall000s/SunOS/plplot/include \ -DCMAKE_INSTALL_INFODIR=/home/hall000s/SunOS/plplot/share/info \ -DCMAKE_INSTALL_LIBDIR=/home/hall000s/SunOS/plplot/lib \ -DCMAKE_INSTALL_MANDIR=/home/hall000s/SunOS/plplot/share/man \ -DDEFAULT_NO_DEVICES=ON \ -DDEFAULT_NO_BINDINGS=ON \ -DBUILD_SHARED_LIBS=OFF \ -DPKG_CONFIG_EXECUTABLE=/bin/pkg-config \ -DPLD_ps=ON \ ../plplot-5.7.4 When the above cmake command is executed it shows the following output. -- Check for working C compiler: /usw/ude/SunOS/bin/gcc -- Check for working C compiler: /usw/ude/SunOS/bin/gcc -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: /usw/ude/SunOS/bin/c++ -- Check for working CXX compiler: /usw/ude/SunOS/bin/c++ -- works -- Checking whether system has ANSI C header files -- Looking for include files StandardHeadersExist -- Looking for include files StandardHeadersExist - found -- Performing Test memchrExists -- Performing Test memchrExists - Success -- Performing Test freeExists -- Performing Test freeExists - Success -- Check for whether ctype.h macros work on characters with the high bit set. -- High-bit characters - work -- ANSI C header files - found -- Looking for include files HAVE_UNISTD_H -- Looking for include files HAVE_UNISTD_H - found -- Looking for include files HAVE_TERMIOS_H -- Looking for include files HAVE_TERMIOS_H - found -- Looking for include files HAVE_STDINT_H -- Looking for include files HAVE_STDINT_H - not found. -- Performing Test HAVE_SYS_WAIT_H -- Performing Test HAVE_SYS_WAIT_H - Success -- Looking for DIR in sys/types.h;dirent.h -- Looking for DIR in sys/types.h;dirent.h - found -- Check for signal return type in <signal.h> -- Check for signal handler return type type void - found -- Looking for popen -- Looking for popen - found -- Looking for usleep -- Looking for usleep - found -- Looking for isinf -- Looking for isinf - not found -- Looking for finite -- Looking for finite - found -- Looking for isnan -- Looking for isnan - found -- SWIG was not found. Please specify Swig executable location -- Looking for XOpenDisplay in /lib/libX11.so;/lib/libXext.so -- Looking for XOpenDisplay in /lib/libX11.so;/lib/libXext.so - found -- Looking for gethostbyname -- Looking for gethostbyname - not found -- Looking for gethostbyname in nsl -- Looking for gethostbyname in nsl - found -- Looking for connect -- Looking for connect - not found -- Looking for connect in socket -- Looking for connect in socket - found -- Looking for remove -- Looking for remove - found -- Looking for shmat -- Looking for shmat - found -- Looking for IceConnectionNumber in ICE -- Looking for IceConnectionNumber in ICE - found -- X11_FOUND = 1 -- X11_INCLUDE_DIR = /usr/include -- X11_COMPILE_FLAGS = -I/usr/include -- X11_LIBRARIES = -lSM;-lICE;/lib/libX11.so;/lib/libXext.so;-lsocket;-lnsl -- X11_LIBRARY_DIR = /lib -- ENABLE_tcl is OFF so disabling everything else that is Tcl/Tk related -- Check for NaN awareness in C compiler -- Check for NaN awareness in C compiler - found -- WARNING: qhull library not found. Setting HAVE_QHULL to OFF. -- Looking for pkg-config - not found -- WARNING: Install-tree build will be disabled. -- WARNING: pango not found because pkg-config not available. -- WARNING: Shared libraries not built. Setting ENABLE_DYNDRIVERS OFF. -- WARNING: ENABLE_tk OFF. Setting PLD_tk, PLD_ntk, and PLD_tkwin OFF. -- WARNING: wxWidgets not found so setting PLD_wxwidgets to OFF. CMake Error: Error in cmake code at /home/hall000s/SunOS/plplot-5.7.4/lib/csa/CMakeLists.txt:45: INSTALL TARGETS given no ARCHIVE DESTINATION for static library target "csirocsa". Current CMake stack: /home/hall000s/SunOS/plplot-5.7.4 /lib/csa/CMakeLists.txt CMake Error: Error in cmake code at /home/hall000s/SunOS/plplot-5.7.4/src/CMakeLists.txt:240: INSTALL TARGETS given no ARCHIVE DESTINATION for static library target "plplotd". Current CMake stack: /home/hall000s/SunOS/plplot-5.7.4/src/CMakeLists.txt Summary of CMake build system results for PLplot Install location variables which can be set by the user: CMAKE_INSTALL_PREFIX: CMAKE_INSTALL_EXEC_PREFIX CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR CMAKE_INSTALL_DATADIR CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_INCLUDEDIR CMAKE_INSTALL_INFODIR CMAKE_INSTALL_MANDIR Derived install location variables: DATA_DIR /plplot5.7.4 LIB_DIR INCLUDE_DIR /plplot BIN_DIR CMAKE_INSTALL_BINDIR TCL_DIR /plplot5.7.4/tcl PYTHON_INSTDIR DRV_DIR /plplot5.7.4/driversd DOC_DIR /doc/plplot MAN_DIR INFO_DIR Other important CMake variables: CMAKE_SYSTEM_NAME: SunOS UNIX: 1 WIN32: APPLE: MSVC: (MSVC_VERSION: ) MINGW: MSYS: CYGWIN: BORLAND: WATCOM: SWIG_FOUND: FALSE PERL_FOUND: YES X11_FOUND: 1 CMAKE_BUILD_TYPE: CMAKE_C_COMPILER CMAKE_C_FLAGS: /usw/ude/SunOS/bin/gcc LIB_TAG: d ENABLE_DYNDRIVERS: OFF DEVICES_LIST: ps DRIVERS_LIST: ps Library options: BUILD_SHARED_LIBS: OFF PL_DOUBLE: ON Optional libraries: HAVE_QHULL: OFF WITH_CSA: ON HAVE_FREETYPE: HAVE_PTHREAD: HAVE_AGG: Language Bindings: ENABLE_f77: OFF ENABLE_f95: OFF ENABLE_cxx: OFF ENABLE_java: OFF ENABLE_python: OFF ENABLE_octave: OFF ENABLE_tcl: OFF ENABLE_itcl: OFF ENABLE_tk: OFF ENABLE_itk: OFF ENABLE_pdl: OFF ENABLE_wxwidgets: OFF ENABLE_gnome2: OFF ENABLE_pygcw: OFF ENABLE_ada: OFF Notice that it did not find my pkg-config executable even though the path I gave it is correct. This occurs with some of the devices and bindings as well. However if I was to use ccmake and enter the same paths that I am using for cmake I have success. Has anyone ran into any problems like this? I appreciate any help with this problem. Thank you in advance, Scott |