This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gnuplot won't work with new net release


> On Thu, Apr 20, 2000 at 02:51:56AM -0700, Tom Weichmann wrote:
> >> On Wed, Apr 19, 2000 at 11:04:42PM -0700, Tom Weichmann wrote:
> >> >	I am running octave 2.0.13 on the cygwin platform.  Octave 
> >> >saves its plot data to a temp file, then points gnuplot to that
> >> >file in order to plot it.  The problem is that gnuplot only
> >> >understands directories in the c:/tmp form and octave understands
> >> >//c/tmp.  In B20.1 I set an environment variable TMPDIR to c:/tmp,
> >> >and both programs liked it.  The new net release translates this
> >> >environment variable to /cygdrive/c/tmp/, and gnuplot can not
> >> >understand it.  Is there any way to keep cygwin from making this
> >> >translation?  Any other ideas?
> >> 
> >> TMPDIR is being translated so that UNIXy things which rely on it,
> >> like configure will work correctly.
> >> 
> >> What happens if you just don't set the environment variable at all?
> >> Does that work any better?
> >> 
> >> cgf
> >
> >	By not setting the TMPDIR variable gnuplot tries to look in /tmp for
> >the data files it uses, but of course gnuplot can't understand /tmp
> >so it can not find the file it is looking for.
> 
> /tmp is a valid Windows directory.  It refers the tmp directory on the
> root of the current drive.
> 
> cgf
> 

I am not sure what you mean.  I opened up a dos prompt and tried 
cd /tmp and received an invalid switch error.  If I cd %tmp% it takes 
me to C:\windows\temp, but that does not work in cygnus.  I guess 
that the only fix to this is to port gnuplot to the cygwin platform, 
instead of tring to get cygwin to communicate with the win32 port.  
I heard once that Mumit Kahn had some kind of patch for gnuplot, 
but I'm not sure exactly what it was.  I was hoping that there was 
some kind of work around for this, but I can not think of anything.  
Is there any way to set the CYGWIN env variable to prevent this 
translation of file names?

Thanks,

Tom Weichmann

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]