This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Cygwin /tmp\foo behaviour
- To: Cygwin-Xfree <cygwin-xfree at sourceware dot cygnus dot com>
- Subject: Re: Cygwin /tmp\foo behaviour
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Sun, 11 Jun 2000 23:01:27 -0400
- References: <20000612025000.9454.qmail@web4605.mail.yahoo.com>
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