Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <3948FB1C.1BFF4CD0@ece.gatech.edu> Date: Thu, 15 Jun 2000 11:49:48 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: earnie_boyd AT yahoo DOT com CC: Steve Kelem , Cygwin Subject: Re: Problem compiling perl module Term::ReadKey under cygwin References: <20000615124432 DOT 22399 DOT qmail AT web106 DOT yahoomail DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Earnie Boyd wrote: > > --- "Charles S. Wilson" wrote: > -8<- > > > > CYGWIN LIST: > > > > I tracked down the problem: the choose_temp_base() routine in libiberty > > (which is linked by dllwrap.exe) defines '\\' as the path separator on > > all _WIN32 platforms. This routine checks the environment variable > > $TMPDIR, $TMP, and $TEMP, followed by {DIRSEP}tmp, and > > {DIRSEP}usr{DIRSEP}tmp. So, in my case $TEMP=/tmp. Then, the routine > > adds {DIRSEP}ccXXXXXX where 'X' is a digit. > > > > The code I'm looking at, which I updated from CVS yesterday uses a '/' for > DIR_SEPARATOR if __CYGWIN__ is defined. The macro DIRSEP doesn't exist. Thbe > relavent code is: Yep. I was looking at the cygwin gcc-2.95.2-1-src.tar.gz source code, which was used to build the version of gcc everyone (until last night) was using. However, even that version doesn't use 'DIRSEP' -- it uses 'DIR_SEPARATOR' but I didn't feel like typing that four or five times in my message. Sorry if that caused confusion. > > > Therefore, '/tmp\ccXXXXXX'. > > > > To whom should a patch for libiberty be sent? > > > > I don't think one is needed. > You are correct. And I am relieved. :-) --Chuck -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com