Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Rafael Laboissiere <laboissiere@ps...>]

* Rafael Laboissiere <laboissiere@...> [2003-02-06 23:50]:

> * Alan W. Irwin <irwin@...> [2003-02-06 10:45]:
> 
> > P.S.  the only options that should affect the C examples are
> > --enable-dyndrivers --with-double (which are common to Rafael and Joao's
> > options) and --disable-static (which Joao has and Rafael does not).
> > 
> > Thus, I bet there is some problem with the present dynamic drivers
> > configuration or implementation that is incompatible with --disable-static.
> > I hope that strong clue allows Rafael to find and fix the problem without
> > too much further effort.
> 
> Well, when I use:
> 
>     ./configure --prefix=/var/tmp/plplot --enable-octave --enable-dyndrivers \
>                 --disable-static --with-double \
>  		--disable-python --disable-tcl --disable-itcl
> 
> then everything works fine.  Notice that the --disable-static option has
> been included above.

I investigated this further and I think that you are following the wrong
trail with --disable-static.  Also, your assumption that the only options
that affect the C examples are --enable-dyndrivers, --with-double, and
--disable-static is wrong.  The option --disable-tcl *does* affect the C
example.

This is the minimal pair that I found:

    C examples segfault:
        ./configure --enable-dyndrivers   

    C examples work fine:
        ./configure --enable-dyndrivers --disable-tcl

I think I am getting close to the source of the problem and that has nothing
to do with --disable-static.

Alan, could you please confirm the minimal pair above?

-- 
Rafael

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Rafael Laboissiere <laboissiere@ps...>]

* Alan W. Irwin <irwin@...> [2003-02-06 10:09]:

> I think you need quotes around the -I option to bootstrap.sh as above
> (contrary to your commit message).  Otherwise, the $1 in bootstrap.sh will
> just catch the -I and miss the rest.

That's fixed, see cvs commit log.

-- 
Rafael

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Rafael Laboissiere <laboissiere@ps...>]

* Alan W. Irwin <irwin@...> [2003-02-06 10:45]:

> P.S.  the only options that should affect the C examples are
> --enable-dyndrivers --with-double (which are common to Rafael and Joao's
> options) and --disable-static (which Joao has and Rafael does not).
> 
> Thus, I bet there is some problem with the present dynamic drivers
> configuration or implementation that is incompatible with --disable-static.
> I hope that strong clue allows Rafael to find and fix the problem without
> too much further effort.

Well, when I use:

    ./configure --prefix=/var/tmp/plplot --enable-octave --enable-dyndrivers \
                --disable-static --with-double \
 		--disable-python --disable-tcl --disable-itcl

then everything works fine.  Notice that the --disable-static option has
been included above.

Weird.

-- 
Rafael

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Alan W. Irwin <irwin@be...>]

P.S.  the only options that should affect the C examples are
--enable-dyndrivers --with-double (which are common to Rafael and Joao's
options) and --disable-static (which Joao has and Rafael does not).

Thus, I bet there is some problem with the present dynamic drivers
configuration or implementation that is incompatible with --disable-static.
I hope that strong clue allows Rafael to find and fix the problem without
too much further effort.

Alan
__________________________
Alan W. Irwin
email: irwin@...
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
__________________________

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Alan W. Irwin <irwin@be...>]

On Thu, 6 Feb 2003, Alan W. Irwin wrote:
> Next, I will try Joao's set of options starting from fresh checkout.

Everything done identically from fresh checkout except for

./configure --prefix=/usr/local/plplot_at --enable-octave \
--enable-dyndrivers --disable-static --with-double > & configure.out

AND THE ANSWER IS....

immediate segfault from x01c and x08c (I didn't bother to try anything else).

So we really do live in a rational universe.  The problem Joao found, and
I confirmed yesterday still exists, and it depends on the exact configure
options above and disappears if you use Rafael's options.

Rafael, do you confirm this?

Joao, I still think it is important for you to confirm that Rafael's exact
set of options works on your system so we know we are all on the same page.

Alan

__________________________
Alan W. Irwin
email: irwin@...
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
__________________________

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Alan W. Irwin <irwin@be...>]

On Thu, 6 Feb 2003, Rafael Laboissiere wrote:

> * Alan W. Irwin <irwin@...> [2003-02-05 16:56]:
>
> > If you had different configure options than Joao and me but are too tired
> > to re-run the test, could you at least tell us what those configuration
> > options are?  I might find they work on my system which would imply the bug
> > is configure option dependent and not autotools version dependent.
>
>
> Here is exactly what I am doing.
>
>     $ rm -rf plplot
>     $ cvs -d rlaboiss@...:/cvsroot/plplot co plplot
>     $ cd plplot
>     $ ./bootstrap.sh
>     $ destdir=/var/tmp/plplot
>     $ ./configure  --prefix=$destdir --disable-tcl --disable-itcl \
>                    --disable-python --enable-dyndrivers --with-double
>     $ rm -rf $destdir
>     $ make install
>     $ cd examples/c
>     $ make x01c
>     $ ./x01c -dev xwin


I confirm that set of options works, and we are back in a rational universe
again after 24 hours where I wasn't sure what kind of universe we were in
....;-)

I will need more investigation to see whether Joao's set of options still
don't work.  There is some ambiguity here because I realize there was a
possibility that my old "system" versions of autotools were interfering.
(My path pointed to the new versions, but some of the old configuration
files might have been interfering.) So the first thing I did was remove
those system versions completely.

apt-get --purge remove autoconf libtool
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
  autoconf* autoconf2.13* automake1.5* libtool*
  0 packages upgraded, 0 newly installed, 4 to remove and 0  not upgraded.
  Need to get 0B of archives. After unpacking 5022kB will be freed.
  Do you want to continue? [Y/n]
  (Reading database ... 92196 files and directories currently installed.)
  Removing automake1.5 ...
  Removing libtool ...
  Removing autoconf ...
  Removing autoconf2.13 ...
  dpkg - warning: while removing autoconf2.13, directory /etc/autoconf2.13'
not empty so not removed.
Removing diversion of /usr/bin/autoconf to /usr/bin/autoconf2.50 by
autoconf2.13'
Removing diversion of /usr/bin/autoheader to /usr/bin/autoheader2.50 by
autoconf2.13'
Removing diversion of /usr/bin/autoreconf to /usr/bin/autoreconf2.50 by
autoconf2.13'
Purging configuration files for autoconf2.13 ...
root@...> ls /etc/autoconf2.13/
root@...> rmdir /etc/autoconf2.13/

(note the autoconf2.13 above which always adds some version uncertainty if
you are using the Debian versions of the autotools.) That is why I keep
urging Rafael to get rid of his Debian versions of autotools to be
consistent with the rest of us, but in this case it apparently does not make
a difference because I confirm his result when I am using the latest stable
version of autotools from FSF.

Fresh plplot checkout as of 16:46 UT.

./bootstrap.sh '-I /home/software/autotools/install/share/libtool/'
Running aclocal (GNU automake) 1.7.2... done
Running autoheader (GNU Autoconf) 2.57... done
Running automake (GNU automake) 1.7.2...configure.ac: installing ./install-sh'
configure.ac: installing ./mkinstalldirs'
configure.ac: installing ./missing'
configure.ac:456: installing ./config.guess'
configure.ac:456: installing ./config.sub'
configure.ac:456: required file ./ltmain.sh' not found
Makefile.am:25: required directory ./libltdl does not exist
bindings/c++/Makefile.am: installing ./depcomp'
drivers/Makefile.am: installing ./compile'
Makefile.am:25: required directory ./libltdl does not exist
 done
Running libtoolize (GNU libtool) 1.4.3... done
Running autoconf (GNU Autoconf) 2.57... done

I think you need quotes around the -I option to bootstrap.sh as above
(contrary to your commit message).  Otherwise, the $1 in bootstrap.sh will
just catch the -I and miss the rest.

rm -rf /usr/local/plplot_at

./configure --prefix=/usr/local/plplot_at --disable-tcl --disable-itcl \
--disable-python --enable-dyndrivers --with-double > & configure.out

make >& make.out
make install >& make_install.out

All the *.out files looked fine.

cd /usr/local/plplot_at/lib/plplot5.2.0/examples
cd c ; make ; cd c++ ; make ; cd f77 ; make ; cd ..
./plplot-test.sh
Plplot library version: 5.2.0
Opened x01c.ps
Opened x02c.ps
Opened x03c.ps
Opened x04c.ps
Opened x05c.ps
Opened x06c.ps
Opened x07c.ps
Opened x08c.ps
Opened x09c.ps
Opened x10c.ps
Opened x11c.ps
Opened x12c.ps
Opened x13c.ps
Opened x15c.ps
Opened x16c.ps
Opened x18c.ps
Opened x19c.ps
Opened x01cc.ps
Opened x01f.ps
Opened x02f.ps
Opened x03f.ps
Opened x04f.ps
Opened x05f.ps
Opened x06f.ps
Opened x07f.ps
Opened x08f.ps
Opened x09f.ps
Opened x10f.ps
Opened x11f.ps
Opened x12f.ps
Opened x13f.ps
Opened x16f.ps

All these results are identical with the plplot-5.2.0 results.

Joao, do you confirm this set of options is working for you as well
(after removing all traces of old autotools)?

Next, I will try Joao's set of options starting from fresh checkout.

Alan

Alan W. Irwin
email: irwin@...
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
__________________________

Re: [Plplot-devel] New way of getting device info from dyndrivers

[Rafael Laboissiere <laboissiere@ps...>]

* Alan W. Irwin <irwin@...> [2003-02-05 16:56]:

> If you had different configure options than Joao and me but are too tired
> to re-run the test, could you at least tell us what those configuration
> options are?  I might find they work on my system which would imply the bug
> is configure option dependent and not autotools version dependent.

Just a comment on this:  what makes me think that the problem is related to
the autotools is the original report by Joao:

* João Cardoso <jcard@...> [2003-02-05 21:06]:

> | > (gdb) run -dev xwin
> | > Starting program: /usr/local/test/lib/plplot5.2.0/examples/c/x01c
> | > -dev xwin
> | >
> | > Program received signal SIGSEGV, Segmentation fault.
> | > 0x0806a46e in lt_dlsym (handle=0x807b0e0,
> | >     symbol=0xbfffef50 "DEVICE_INFO_pstex") at ltdl.c:3330
> | > [...]

The bug has been caused by a call to the function lt_dlsym in ltdl.c, more
precisely when it is called with argument "DEVICE_INFO_pstex".  Of course,
this is related to my last changes in the code.  However, I can hardly see
what I am doing wrong, since I cannot replicate the bug.  I tend to believe
that it is related to version problems in the Autotools.  

That said, I really hope that this is a configuration option problem, which
would be easier to fix...

-- 
Rafael

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Rafael Laboissiere <laboissiere@ps...>]

* Alan W. Irwin <irwin@...> [2003-02-05 16:56]:

> If you had different configure options than Joao and me but are too tired
> to re-run the test, could you at least tell us what those configuration
> options are?  I might find they work on my system which would imply the bug
> is configure option dependent and not autotools version dependent.


Here is exactly what I am doing.

    $ rm -rf plplot
    $ cvs -d rlaboiss@...:/cvsroot/plplot co plplot
    $ cd plplot
    $ ./bootstrap.sh
    $ destdir=/var/tmp/plplot
    $ ./configure  --prefix=$destdir --disable-tcl --disable-itcl \
                   --disable-python --enable-dyndrivers --with-double
    $ rm -rf $destdir
    $ make install
    $ cd examples/c
    $ make x01c
    $ ./x01c -dev xwin

All the C demos compile and work fine here.

I am now using Libtool 1.4.3 from Debian unstable.  Please noticed that I had
to make changes in bootstrap.sh in order to get this version of Libtool
working properly with Autoconf 2.57 and Automake 1.7.2 (see my last cvs
commit).

If you guys cannot replicate my successful build with the latest version of
bootstrap.sh, I will be completely puzzled.

-- 
Rafael

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Alan W. Irwin <irwin@be...>]

On Thu, 6 Feb 2003, Rafael Laboissiere wrote:

> * Alan W. Irwin <irwin@...> [2003-02-05 15:18]:
>
> > You didn't say so, but I presume you configured with exactly same options
> > and have latest stable autotools like Joao and me (not Debian ones).
>
> I have :
>
>     $ ./bootstrap.sh
>     Running aclocal (GNU automake) 1.7.2... done
>     Running libtoolize (GNU libtool) 1.4.2a... done
>     Running autoheader (GNU Autoconf) 2.57... done
>     Running automake (GNU automake) 1.7.2... done
>     Running autoconf (GNU Autoconf) 2.57... done

[then got diverted into version stuff which might be relevant and forgot to
mention the configure options].

If you had different configure options than Joao and me but are too tired
to re-run the test, could you at least tell us what those configuration
options are?  I might find they work on my system which would imply the bug
is configure option dependent and not autotools version dependent.

Joao's further comment about his quite different gcc version seems to take
that version dependence out of contention.

Alan

__________________________
Alan W. Irwin
email: irwin@...
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
__________________________

Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Joao Cardoso <jcard@fe...>]

On Wednesday 05 February 2003 23:21, Rafael Laboissiere wrote:
> * Alan W. Irwin <irwin@...> [2003-02-05 15:18]:
> > You didn't say so, but I presume you configured with exactly same opt=
ions
> > and have latest stable autotools like Joao and me (not Debian ones).
>
> I have :
>
>     $ ./bootstrap.sh
>     Running aclocal (GNU automake) 1.7.2... done
>     Running libtoolize (GNU libtool) 1.4.2a... done
>     Running autoheader (GNU Autoconf) 2.57... done
>     Running automake (GNU automake) 1.7.2... done
>     Running autoconf (GNU Autoconf) 2.57... done
>
> I am not using the latest version of libtool (1.4.3).

I noticed that "file x01c" in the build tree reports an executable  ELF, =
not a=20
script file as is usual with libtool. That's why I make x01c in the insta=
ll=20
directory, but I still get an executable!

>  That may explain the
> difference.  I will try to use 1.4.3, but that is not going to be befor=
e
> this weekend (I have two busy days before me).
>
> > Or maybe it is gcc version?
> >
> > I have Debian woody
> >
> > Version: 2:2.95.4-14

mine is gcc-3.2

>
> I have here:
>
>   Version: 2:2.95.4-17