Re: [Plplot-devel] done with config changes

[Alan W. I. <ir...@be...>]

On Sun, 20 Jan 2002, Maurice LeBrun wrote:

> My last round of commits fixed all the config problems I mentioned
> previously.

Thanks, Maurice.

> Please try it out.

The results of the near-default

./configure --disable-java --without-shlib

that I did for Joao seemed to be fine.  (In fact too fine because I could
not reproduce his problem.)

I also tried

./configure --disable-drivers --enable-png --enable-dyndrivers

and I got

devices:         png jpeg cgm xwin tk

Available device drivers
static:          xwin tk
dynamic:         gd cgm

All these devices worked fine, but I don't understand why --disable-drivers
is not affecting cgm.  I worked really hard to make all the cgm stuff in
plplot/cf/*.in files identical to what was done for gd or png/jpeg as
appropriate.  Also, I just checked that again, and I cannot find anything.
Nevertheless something is wrong for cgm (and perhaps also for jpeg and png
or gd since cgm follows them), and I hope you find it.  Perhaps there is a
more mundane reason why xwin and tk are still there despite the
--disable-drivers option, but again I don't understand this.

(I tried the same thing with default static drivers and got the same result,
all 5 devices were available.)

Finally, I tried a super-kill of everything but device png.

configure --disable-drivers --disable-jpeg --disable-cgm \
--disable-tk --disable-xwin --enable-png --enable-dyndrivers

That worked to isolate just the png device for the gd driver with none of
the other 4 devices that were active before, but I don't see why a simple
--disable-drivers wouldn't have given the same thing.

Finally, I noticed the following compilation messages for the first
configuration (but none of the others, interestingly).

tk.o(.text+0x1c70): the use of tmpnam' is dangerous, better use mkstemp'
tk.o(.text+0x1c70): the use of tmpnam' is dangerous, better use mkstemp'
plframe.o(.text+0x291d): the use of tmpnam' is dangerous, better use mkstemp'

I suspect this message means our use of tmpnam is opening a security hole.
I don't know how serious this is, but, Maurice, if you know how to use
mkstemp then you may want to switch to it from tmpnam.

Alan