Re: Cygwin /tmp\foo behaviour

["Trevor Forbes" <trevorforbes at ozemail dot com dot au>]

For info.
I removed all references to TMP TEMP TMPDIR......

Same result:
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../i686-pc-cygwin/bin/ld:
Can't open base file /tmp\cc001024.base

Trevor


----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: "Cygwin-Xfree" <cygwin-xfree@sourceware.cygnus.com>
Sent: Monday, 12 June 2000 12:31
Subject: Re: Cygwin /tmp\foo behaviour


> On Sun, Jun 11, 2000 at 07:50:00PM -0700, Suhaib Siddiqi wrote:
> >
> >> On Mon, Jun 12, 2000 at 10:41:30AM +0930, Trevor Forbes wrote:
> >>>So If I understand you correctly "/tmp\cc017659.base" should not link
> >>>anyway as ld will always be looking for "/tmpcc017659.base" which will
> >>>never exist?
> >>
> >>Nope.  You were trying to test out something by using a \ character at
> >>the bash command line.  In your test case, bash ate the \ character
> >>just like it would on UNIX.  The "problem" that you saw was unrelated
> >>to the problem in gcc.
> >
> >He is not trying to test something.  The /tmp/xxxxx.base files are
> >generated during X lib DLLs creation.  The ld is trying to read
> >/tmp\xxxx.base which on bash returns /tmpxxxxx.base, therefore he gets
> >"no such file" error.
>
> He was testing something by typing a command in bash.  That is what I
> meant.  That is why I mentioned "bash" and then talked about "gcc".  I
> was trying to clarify the fact that Trevor's attempt to test the problem
> by using a 'ld' command in bash was unrelated to the problem in gcc.
>
> >With my Cygwin setup I have not seen this problem, although I do have
> >TEMP, TMP and TEMPDIR in my ENV
> >
> >TEMP=G:\Temp
> >TMP=G:\Temp
> >TMPDIR=/tmp
>
> I would guess that your TMPDIR takes precedence, then.  I'm not 100%
> certain what causes the problem.
>
> cgf
>
>