Re: [Plplot-devel] done with config changes + STATUS QUESTION

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

On Mon, 21 Jan 2002, Maurice LeBrun wrote:

> Alan W. Irwin writes:
>  > 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.

I woke up this morning (apparently close to when you finished working hard
all night.... thanks!) with the same idea that it had something to do with
the extra library configuration that occurs for certain drivers.  Thanks for
investigating further to determine this special configuration was still
necessary.  I agree, let's continue to live with it.

>  > tk.o(.text+0x1c70): 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.

Thanks for looking into this.

STATUS QUESTION:

So is there anything left on our plates other than the fortran problems that
Joao has found?  (BTW, I view that bug as serious.  For now, Joao has to
deal with this bug on his own. Since I cannot reproduce it on my system, I
am reduced to helping him only with guess work.  Those with some fortran
knowledge, please do take a few minutes to attempt reproducing the bug on your
systems on the off chance that you can give him some help to solve this
quickly.)

Alan