Re: [Plplot-devel] done with config changes

[Maurice L. <mj...@ga...>]

Alan W. Irwin writes:
 > On Sun, 20 Jan 2002, Maurice LeBrun wrote:
 > 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. ...

It's because of the following lines in configure.in, near the top:

#explicit default values must be specified here for library and header  
#searching to work right for the following variables.  Note these variables 
#also have a driver role to play, but unlike these, pure-driver variables 
#(e.g., enable_tek4010) do not require a default to be specified here. 
enable_gnome=no 
enable_ntk=no 
enable_png=yes 
enable_jpeg=yes 
enable_cgm=yes 
enable_tk=yes 
enable_xwin=yes 
 
--disable-drivers only sets the default to "no", and doesn't override any
explicitly enabled devices, which these are (equivalent to command line
settings).  Apparently they do serve a purpose for getting library linkage
right under Linux -- I just tried without them and the build failed (to my
surprise).  There may be a better way to fix it, I dunno.  But anyway
apparently works as expected.  You can always use explicit disabling of
devices, which I do, from my ~/config/cf_plplot.in file.

 > 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.

Theoretically there is a problem, but I'm not worrying about it.  tmpnam is
POSIX, mkstemp is not.  Maybe eventually I'll do some configure stuff to use
mkstemp where available, otherwise tmpnam, just to shut up gcc.  But not that
important to me.

-- 
Maurice LeBrun    mj...@ga...