From: Koen v. d. D. <kvd...@ea...> - 2003-12-24 12:01:34
|
Hi, Thanks to some recent messages on this list, I was able to compile plplot (5.2.1) on Mac OS X 10.3.2. However, according to the table that's shown after the configure step, it doesn't compile for other languages than C++. I know that python and tcltk are standard on OS X. I checked the docs, but couldn't find how to configure the compilation (besides using --enable-python). What's the trick for doing this? thanks, - Koen. |
From: Alan W. I. <ai...@us...> - 2003-12-24 18:28:57
|
On 2003-12-24 07:00-0500 Koen van der Drift wrote: > Hi, > > Thanks to some recent messages on this list, I was able to compile > plplot (5.2.1) on Mac OS X 10.3.2. However, according to the table > that's shown after the configure step, it doesn't compile for other > languages than C++. I know that python and tcltk are standard on OS X. > I checked the docs, but couldn't find how to configure the compilation > (besides using --enable-python). What's the trick for doing this? > First make sure you have the development packages (those which include the headers) installed for python and tcl/tk/itcl/itk. Then set environment variables before you execute ./configure to help that script find the headers and libraries. Python: PY_VERSION=`python -c 'import sys ; print sys.version[0:3]'` export PYTHON_INC_DIR=/usr/include/python${PY_VERSION}/ The first command is just a trick to get the python version that is normally part of the include directory name, but if you know your python version in advance it won't be necessary. The export command is the important one. Adjust that line (including the correct version number for your default python) to wherever your python headers are located. Tcl/Tk: We have yet to find a decent autotools macro to help configure Tcl/Tk. The ones that come with our versions of Tcl/Tk seem way out of date (probably because autotools have been such a moving target over the last year or so). Thus, a lot more environment variables are currently required to help ./configure find tcl/tk stuff. You may have to play a bit with the following environment variables (see sysloc.in for how they are used) until you get the right combination: TCLINCDIR TCLLIBDIR TKINCDIR TKLIBDIR Once your configure output shows that both tcl and tk have been found you can also control finding the include and library directories for itcl and itk using ITCLINCDIR ITCLLIBDIR ITKLIBDIR (I have forgotten why we don't use ITKINCDIR, but apparently it is not needed.) Also note you can do a lot in Tcl/Tk using PLplot without itcl and itk so it is no disaster if those parts of the tcl/tk interface to PLplot are turned off. Let us know how it goes. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the PLplot scientific plotting software package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Koen v. d. D. <kvd...@ea...> - 2003-12-25 18:02:00
|
On Dec 24, 2003, at 1:28 PM, Alan W. Irwin wrote: > Python: > > PY_VERSION=`python -c 'import sys ; print sys.version[0:3]'` > export PYTHON_INC_DIR=/usr/include/python${PY_VERSION}/ > > The first command is just a trick to get the python version that is > normally > part of the include directory name, but if you know your python > version in > advance it won't be necessary. The export command is the important > one. > Adjust that line (including the correct version number for your default > python) to wherever your python headers are located. Thanks for the input. From previous postings on Mac OSX and plplot I understand that I need to use --disable-shared. However, when shared is disabled, python will be disabled by the configure script. I could compile plplot with shared enabled, but I don't know yet whether the package is usable. I'll do some more testing in the next couple of days if I can find some time during the holidays. Besides python, X11 and tcltk, are there any other packages needed for plplot? thanks, - Koen. |
From: Alan W. I. <ai...@us...> - 2003-12-25 19:55:39
|
On 2003-12-25 13:00-0500 Koen van der Drift wrote: > On Dec 24, 2003, at 1:28 PM, Alan W. Irwin wrote: > > > Python: > > > > PY_VERSION=`python -c 'import sys ; print sys.version[0:3]'` > > export PYTHON_INC_DIR=/usr/include/python${PY_VERSION}/ > > > > The first command is just a trick to get the python version that is > > normally > > part of the include directory name, but if you know your python > > version in > > advance it won't be necessary. The export command is the important > > one. > > Adjust that line (including the correct version number for your default > > python) to wherever your python headers are located. > > Thanks for the input. From previous postings on Mac OSX and plplot I > understand that I need to use --disable-shared. That's only needed (as a temporary workaround) for the fortran case. Also, dynamic drivers don't work for all cases (we still haven't come up with a fix for that bug) so you must always specify --disable-dyndrivers. However, if you specify --disable-f77 --disable-dyndrivers (and use the default --enable-shared), shared libraries and python apparently (see discussions in September on plplot-devel) work well. Note, some patches had to be applied to PLplot-5.2.1 to get that to work smoothly for old (10.1?) Mac OS X, but the latest PLplot cvs does not work with Mac OS X 10.3 (still no fix for that bug as well). I am sorry everything is in a bit of disarray with Mac OS X and PLplot, but we all three of Mac OS X, autotools, and PLplot are rapidly moving targets. Also, bug fixing is slow because no PLplot developer has direct Mac OS X access, and we must rely on indirect actions of users to help us debug for that platform as a consequence. > Besides python, X11 and tcltk, are there any other packages needed for > plplot? In actual truth none of the above are needed. For example, if all the above are disabled, you could (theoretically, I haven't tried this myself) still run any of the C examples from the command line using -dev psc (our coloured postscript device) or -dev ps (our gray-scale postscript device) and send the file results directly to a printer without X, tcl/tk, or python being installed on your system. What is going on is the configure script has essentially every language interface for PLplot and every device driver enabled by default. You can turn off any of those with the --disable options, (run ./configure --help to look at all options) and it will carry on with the subset of PLplot that you have specified. If configure cannot find needed system resources it will disable even more options itself (with a warning message) and carry on. So if you want everything, look for those warning messages from configure and install the appropriate development package. But you can choose to ignore those warning messages, and the remaining subset of PLplot should work fine. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the PLplot scientific plotting software package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Koen v. d. D. <kvd...@ea...> - 2003-12-26 13:11:55
|
On Dec 25, 2003, at 2:55 PM, Alan W. Irwin wrote: > I am sorry everything is in a bit of disarray with Mac OS X and > PLplot, but > we all three of Mac OS X, autotools, and PLplot are rapidly moving > targets. > Also, bug fixing is slow because no PLplot developer has direct Mac OS > X > access, and we must rely on indirect actions of users to help us debug > for > that platform as a consequence. I'll be glad to help - just don't have much time and resources (knowledge). > In actual truth none of the above are needed. For example, if all the > above > are disabled, you could (theoretically, I haven't tried this myself) > still > run any of the C examples from the command line using -dev psc (our > coloured > postscript device) or -dev ps I tried this, but didn;t get it to work, due to my experience with the command line (I don't have a unix but rather a Mac GUI background :). What is the correct syntax to run the c examples from the command line? thanks, - Koen. |
From: Alan W. I. <ai...@us...> - 2003-12-26 18:12:24
|
On 2003-12-26 08:10-0500 Koen van der Drift wrote: > > On Dec 25, 2003, at 2:55 PM, Alan W. Irwin wrote: > > > I am sorry everything is in a bit of disarray with Mac OS X and > > PLplot, but > > we all three of Mac OS X, autotools, and PLplot are rapidly moving > > targets. > > Also, bug fixing is slow because no PLplot developer has direct Mac OS > > X > > access, and we must rely on indirect actions of users to help us debug > > for > > that platform as a consequence. > > I'll be glad to help - just don't have much time and resources > (knowledge). > > > > In actual truth none of the above are needed. For example, if all the > > above > > are disabled, you could (theoretically, I haven't tried this myself) > > still > > run any of the C examples from the command line using -dev psc (our > > coloured > > postscript device) or -dev ps > > > I tried this, but didn;t get it to work, due to my experience with the > command line (I don't have a unix but rather a Mac GUI background :). > What is the correct syntax to run the c examples from the command line? > > > thanks, > > - Koen. > Here is the detailed cookbook. After make install, do the following to build the examples: cd /tmp (or any other directory accessible to you as an ordinary user) copy the installed examples tree (the trailing period is important): cp -a $prefix/lib/plplot$version/examples . go into the C examples directory and build those examples: cd examples/c make x01c (or drop the x01c from the command to build all C examples) Then in that same directory to execute the built example: ./x01c -dev psc -o temp.ps which creates the result file temp.ps containing the coloured postscript plot of our example 1. BTW, you could help us out a lot (assuming you have MacOS X 10.3) to try the latest cvs snapshot version Rafael just announced. We need confirmation of a report from one user that he could not even configure the cvs version of Plplot with 10.3. Please use an install tree (e.g., --prefix=/tmp/plplot_cvs) completely independent of your 5.2.1 install tree/. You will have to put $prefix/bin first on your path so that e.g., which plplot_libtool gives you the correct version from your cvs snapshot plplot build and install. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the PLplot scientific plotting software package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Koen v. d. D. <kvd...@ea...> - 2003-12-26 19:46:56
|
On Dec 26, 2003, at 1:12 PM, Alan W. Irwin wrote: > BTW, you could help us out a lot (assuming you have MacOS X 10.3) to > try the > latest cvs snapshot version Rafael just announced. We need > confirmation of > a report from one user that he could not even configure the cvs > version of > Plplot with 10.3. Please use an install tree (e.g., > --prefix=/tmp/plplot_cvs) completely independent of your 5.2.1 install > tree/. You will have to put $prefix/bin first on your path so that > e.g., > > which plplot_libtool > > gives you the correct version from your cvs snapshot plplot build and > install. > I've seen that problem too, even with today's snapshot. Here's the output: [RubyTuesday:~/Desktop/plplot-5.2.1.cvs.20031226] koen% ./configure --prefix=/tmp/plplot_cvs --disable-dyndrivers No defaults file found, performing full configure. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for cc option to accept ANSI C... no checking build system type... powerpc-apple-darwin7.2.0 checking host system type... powerpc-apple-darwin7.2.0 checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... /lib/cpp configure: error: C preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. [RubyTuesday:~/Desktop/plplot-5.2.1.cvs.20031226] koen% It goes away if I remove the "--disable-dyndrivers" argument. Then the output looks like this: [RubyTuesday:~/Desktop/plplot-5.2.1.cvs.20031226] koen% ./configure --prefix=/tmp/plplot_cvs No defaults file found, performing full configure. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for lt_dlinit in -lltdl... yes checking for gcc option to accept ANSI C... none needed checking build system type... powerpc-apple-darwin7.2.0 checking host system type... powerpc-apple-darwin7.2.0 checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes ... I am using 10.3.2. - Koen. |
From: Koen v. d. D. <kvd...@ea...> - 2003-12-26 20:28:39
|
On Dec 26, 2003, at 1:12 PM, Alan W. Irwin wrote: > BTW, you could help us out a lot (assuming you have MacOS X 10.3) to > try the > latest cvs snapshot version Rafael just announced. When using ./configure without disabeling the dyndrivers, the compilation eventually halts: ... ./get-drv-info `echo hpgl.la | sed 's/.la//'` > hpgl.rc ltdl.c:2460: failed assertion `dirname' make[2]: *** [hpgl.rc] Error 134 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 [RubyTuesday:~/Desktop/plplot-5.2.1.cvs.20031226] koen% I did not see this with the 5.2.1 release. - Koen. |
From: Rafael L. <rla...@us...> - 2003-12-26 22:10:36
|
* Koen van der Drift <kvd...@ea...> [2003-12-26 15:27]: > On Dec 26, 2003, at 1:12 PM, Alan W. Irwin wrote: > > > BTW, you could help us out a lot (assuming you have MacOS X 10.3) to try > > the latest cvs snapshot version Rafael just announced. > > > When using ./configure without disabeling the dyndrivers, the > compilation eventually halts: > > ... > ./get-drv-info `echo hpgl.la | sed 's/.la//'` > hpgl.rc > ltdl.c:2460: failed assertion `dirname' > make[2]: *** [hpgl.rc] Error 134 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 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 did not see this with the 5.2.1 release. Have you tried to configure the 5.2.1 release with --enable-dyndrivers? -- Rafael |
From: Koen v. d. D. <kvd...@ea...> - 2003-12-28 20:33:15
|
On Dec 26, 2003, at 1:12 PM, Alan W. Irwin wrote: > Then in that same directory to execute the built example: > > ./x01c -dev psc -o temp.ps > > which creates the result file temp.ps containing the coloured > postscript > plot of our example 1. > Yes, that works (tested with latest cvs release)! But it only works if plplot gets installed into /usr/local/. My goal is to create a plplot package for the fink project, which is a debian-type package manager for Mac OS X. Fink installs everything into a special dedicated directory /sw. If I run the examples from /sw/share/plplot/examples, I get an error about fonts: *** PLPLOT ERROR *** Unable to open or allocate memory for font file Program aborted. Does plplot install its own fonts (and where)? - Koen. |