Menu
▾
▴
plplot-devel
|
From: Joao C. <jc...@fe...> - 2003-03-03 20:58:10
|
Hi,
After a fresh cvs checkout, running bootstrap.sh
[jcard@feup] ./bootstrap.sh=20
Running aclocal (GNU automake) 1.7.2... done
Running autoheader (GNU Autoconf) 2.57... done
Running automake (GNU automake) 1.7.2... done
Running libtoolize (GNU libtool) 1.4.3... done
Running autoconf (GNU Autoconf) 2.57... done
taring, ftp to an alphaev6-dec-osf4.0f system, untaring and running conf=
igure=20
gave several errors:
checking for gcc option to accept ANSI C... none needed
checking build system type... ./config.guess: umask: `7077' is not an oct=
al=20
numb
er from 000 to 777
config.guess: cannot create /tmp/config-guess-23584
alphaev6-dec-osf4.0f
checking host system type... alphaev6-dec-osf4.0f
=2E..
checking for mkoctfile... yes
sed: Function s/--compile// ; t END ; d ; : END q cannot be parsed.
checking for octave... yes
sed: Function s/^.*version // ; q cannot be parsed.
warning: broken pipe
sed: Function s/^2.1//p ; d ; q cannot be parsed.
checking for Python.h... no
warning: can't find Python.h, setting enable_python to no
checking for qh_new_qhull in -lqhull... no
checking for KCC... no
=2E..
config.status: executing depfiles commands
configure: configuring in libltdl
configure: running /bin/bash './configure'=20
--prefix=3D/usr/users1/deec/jcard/plplo
t-alf/test '--prefix=3D/usr/users1/deec/jcard/plplot-alf/test'=20
'--disable-static'
--enable-ltdl-convenience --cache-file=3D/dev/null --srcdir=3D.
loading cache /dev/null
=2E/configure: .: /dev/null: not a regular file
=2E..
The summary gave
Optional libraries:
with_freetype: no with_qhull: yes
although qhull was not detected!
Then, after removing all, untaring again and reconfiguring with=20
--prefix=3D<xxx> --disable-static --without-qhull
besides the above errors gave:
bash-2.01$ make
cd . && /bin/bash /usr/users1/deec/jcard/plplot-alf/missing --run autohea=
der
/usr/users1/deec/jcard/plplot-alf/missing: autoheader: command not found
WARNING: `autoheader' is missing on your system. You should only need it=
if
you modified `acconfig.h' or `configure.ac'. You might want
to install the `Autoconf' and `GNU m4' packages. Grab them
from any GNU archive site.
touch ./config.h.in
cd . && /bin/bash ./config.status config.h
make: *** [stamp-h1] Error 139
bash-2.01$ ls -l configure*
-rwx------ 1 jcard docentes 626581 Mar 3 20:20 configure
-rw------- 1 jcard docentes 27320 Mar 3 16:27 configure.ac
configuring a second time and making again worked, but latter
make[2]: Entering directory `/usr/users1/deec/jcard/plplot-alf/include'
cd .. && /bin/bash /usr/users1/deec/jcard/plplot-alf/missing --run autohe=
ader
/usr/users1/deec/jcard/plplot-alf/missing: autoheader: command not found
=2E..
Joao
|
|
From: Rafael L. <lab...@ps...> - 2003-03-03 21:43:05
|
* Joao Cardoso <jc...@fe...> [2003-03-03 20:53]: > After a fresh cvs checkout, running bootstrap.sh > > [jcard@feup] ./bootstrap.sh > Running aclocal (GNU automake) 1.7.2... done > Running autoheader (GNU Autoconf) 2.57... done > Running automake (GNU automake) 1.7.2... done > Running libtoolize (GNU libtool) 1.4.3... done > Running autoconf (GNU Autoconf) 2.57... done > > taring, ftp to an alphaev6-dec-osf4.0f system, untaring and running configure > gave several errors: > > [...] This technique is error-prone. The correct approach is to generate a tarball with "make dist". Unfortunately, make dist does not work perfectly yet (but will for the next release, hopefully). -- Rafael |
|
From: Alan W. I. <ir...@be...> - 2003-03-03 23:54:12
|
On Mon, 3 Mar 2003, Rafael Laboissiere wrote: > * Joao Cardoso <jc...@fe...> [2003-03-03 20:53]: > > > After a fresh cvs checkout, running bootstrap.sh > > > > [jcard@feup] ./bootstrap.sh > > Running aclocal (GNU automake) 1.7.2... done > > Running autoheader (GNU Autoconf) 2.57... done > > Running automake (GNU automake) 1.7.2... done > > Running libtoolize (GNU libtool) 1.4.3... done > > Running autoconf (GNU Autoconf) 2.57... done > > > > taring, ftp to an alphaev6-dec-osf4.0f system, untaring and running configure > > gave several errors: > > > > [...] > > This technique is error-prone. The correct approach is to generate a > tarball with "make dist". Unfortunately, make dist does not work perfectly > yet (but will for the next release, hopefully). I agree you do have to be careful with making a tarball, but on the other hand it is almost as straightforward as avoiding pitfalls when developing with cvs. You must start with a clean tree, and you need the correct version of swig and autotools on your system where you are preparing the tarball. The only peculiar thing is two files need to be touched if you are not using my script. Note that scripts/make_tarball.sh touches two files so that autotools are not invoked on the system where the tarball is being used. That script also does the appropriate swig and perl preparation so you won't need swig or perl on the system where the tarball is being used. Until Rafael can get make dist to work, using this script is probably your best bet for preparing a clean tree for a tarball. Just now, I have commented out getting access to our documentation results from the website because those files are changing. I will put them back in correct form later once our documentation settles down (and if make dist continues not to work), but for now, nobody needs those documentation results. Let me know if you have any trouble generating a tarball with the script and testing it on your Linux system. If the tarball works on Linux (i.e., no autotools or swig execution and build, install, and plplot-test.sh are fine) but does not work on other platforms, that is a pretty clear indication that cross-platform issues have crept into CVS again. 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 Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
|
From: Joao C. <jc...@fe...> - 2003-03-04 01:17:56
|
On Monday 03 March 2003 23:52, Alan W. Irwin wrote: > On Mon, 3 Mar 2003, Rafael Laboissiere wrote: > > * Joao Cardoso <jc...@fe...> [2003-03-03 20:53]: > > > After a fresh cvs checkout, running bootstrap.sh > > > > > > [jcard@feup] ./bootstrap.sh > > > Running aclocal (GNU automake) 1.7.2... done > > > Running autoheader (GNU Autoconf) 2.57... done > > > Running automake (GNU automake) 1.7.2... done > > > Running libtoolize (GNU libtool) 1.4.3... done > > > Running autoconf (GNU Autoconf) 2.57... done > > > > > > taring, ftp to an alphaev6-dec-osf4.0f system, untaring and runnin= g > > > configure gave several errors: > > > > > > [...] > > > > This technique is error-prone. The correct approach is to generate a > > tarball with "make dist". Unfortunately, make dist does not work > > perfectly yet (but will for the next release, hopefully). > > I agree you do have to be careful with making a tarball, but on the oth= er > hand it is almost as straightforward as avoiding pitfalls when developi= ng > with cvs. You must start with a clean tree, and you need the correct > version of swig and autotools on your system where you are preparing th= e > tarball. The only peculiar thing is two files need to be touched if yo= u > are not using my script. > > Note that scripts/make_tarball.sh touches two files so that autotools a= re > not invoked on the system where the tarball is being used. I don't want to make a distro, just be able to quickly test on another=20 architecture (I'm concerned with NaN stuff in nn/csa/plgridd.c). Alan receipt, "touch plConfig.h.in plDevs.h.in", is enough for my needs. Thanks, Joao |
|
From: Alan W. I. <ir...@be...> - 2003-03-04 02:58:34
|
On Tue, 4 Mar 2003, Joao Cardoso wrote: > Alan receipt, "touch plConfig.h.in plDevs.h.in", is enough for my needs. In general, yes, but in specific you have to be careful of what you do and the order you do it. Clean tree, then bootstrap.sh, then touch, then create tarball. Of course, when you use the tarball, you will have to manually turn off tcl and python (java is already disabled by default) if they are on the system at all. I still think it is easier to do clean tree then script then create tarball with no worries about turning off anything afterward when you use the tarball, but that is up to you. 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 Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
|
From: Joao C. <jc...@fe...> - 2003-03-04 03:26:16
|
On Tuesday 04 March 2003 01:13, Joao Cardoso wrote: > On Monday 03 March 2003 23:52, Alan W. Irwin wrote: > > On Mon, 3 Mar 2003, Rafael Laboissiere wrote: > > > * Joao Cardoso <jc...@fe...> [2003-03-03 20:53]: > > > > After a fresh cvs checkout, running bootstrap.sh =2E.. > I don't want to make a distro, just be able to quickly test on another > architecture (I'm concerned with NaN stuff in nn/csa/plgridd.c). As I was afraid, under OSF1-V4.0 libcsa has trouble because of NaNs. libn= n=20 must have the same problem. I ended up trying libcsa with its own test programs, but they fail, and I= =20 trace the problem down to NaNs handling It is increadible how ieee-754 is still "vendor dependent"! Cray is know = to be=20 not conformant, but OSF... Joao |
|
From: Joao C. <jc...@fe...> - 2003-03-04 19:22:12
|
On Tuesday 04 March 2003 03:21, Joao Cardoso wrote: > On Tuesday 04 March 2003 01:13, Joao Cardoso wrote: > > On Monday 03 March 2003 23:52, Alan W. Irwin wrote: > > > On Mon, 3 Mar 2003, Rafael Laboissiere wrote: > > > > * Joao Cardoso <jc...@fe...> [2003-03-03 20:53]: > > > > > After a fresh cvs checkout, running bootstrap.sh > > ... > > > I don't want to make a distro, just be able to quickly test on anothe= r > > architecture (I'm concerned with NaN stuff in nn/csa/plgridd.c). > > As I was afraid, under OSF1-V4.0 libcsa has trouble because of NaNs. li= bnn > must have the same problem. > > I ended up trying libcsa with its own test programs, but they fail, and= I > trace the problem down to NaNs handling > > It is increadible how ieee-754 is still "vendor dependent"! Cray is kno= w to > be not conformant, but OSF... I add some logic in sysloc.in to add the correct CFLAGS when compiling on= a=20 alpha/OSF -- please check it, it occurred to me just now that I did it th= e=20 wrong way, as the problem is not only related with the hardware but also = with=20 the OS. I *think* that linux running in an alpha might not have the probl= em,=20 I'm not sure. It would be nice if you guys with non-linux system could test this new co= de.=20 After the normal configure/make/install, try examples/x21c and report bac= k Thanks, Joao |
|
From: Rafael L. <lab...@ps...> - 2003-03-04 09:42:27
|
[Out of order:] * Joao Cardoso <jc...@fe...> [2003-03-04 01:13]: > Alan receipt, "touch plConfig.h.in plDevs.h.in", is enough for my needs. This is one of the things that is automatically done by "make dist". There are problem other hidden problems that Alan's make_tarball.sh script does not address, but "make dist" will. I will try to put high priority on making "make dist" work. > I don't want to make a distro, just be able to quickly test on another > architecture (I'm concerned with NaN stuff in nn/csa/plgridd.c). It is not a matter of making a distro. What "make dist" does for you is to generate a tarball ready for configure/make, circumventing all those nasty "touch me" problems. Look at it as a sophisticated tar command (you had to do a "tar" before trying on the alpha machine, hadn't you? :-) -- Rafael |
|
From: Joao C. <jc...@fe...> - 2003-03-04 19:14:59
|
On Tuesday 04 March 2003 09:35, Rafael Laboissiere wrote: > [Out of order:] > > * Joao Cardoso <jc...@fe...> [2003-03-04 01:13]: > > Alan receipt, "touch plConfig.h.in plDevs.h.in", is enough for my ne= eds. > > This is one of the things that is automatically done by "make dist". T= here > are problem other hidden problems that Alan's make_tarball.sh script do= es > not address, but "make dist" will. > > I will try to put high priority on making "make dist" work. > > > I don't want to make a distro, just be able to quickly test on anothe= r > > architecture (I'm concerned with NaN stuff in nn/csa/plgridd.c). > > It is not a matter of making a distro. What "make dist" does for you i= s to > generate a tarball ready for configure/make, circumventing all those na= sty > "touch me" problems. Look at it as a sophisticated tar command (you ha= d to > do a "tar" before trying on the alpha machine, hadn't you? :-) OK, OK, I was just in a hurry :) But to "make dist" I have to configure, right? Joao |
|
From: Rafael L. <lab...@ps...> - 2003-03-05 08:03:38
|
* Joao Cardoso <jc...@fe...> [2003-03-04 19:10]: > But to "make dist" I have to configure, right? Yes, but beware that the resulting tarball may lack some important files. I am working on this now. Also, you should always configure --enable-docbook=no (and also --enable-python=no, if you do not have the appropriate version of swig). -- Rafael |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X