Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199902231639.KAA04761@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: "Gary V. Vaughan" <gvaughan AT oranda DOT demon DOT co DOT uk>
cc: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ? 
In-reply-to: Your message of "Tue, 23 Feb 1999 12:57:01 GMT."
             <36D2A59D DOT 603BF54E AT oranda DOT demon DOT co DOT uk> 
Date: Tue, 23 Feb 1999 10:39:09 -0600
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"Gary V. Vaughan" <gvaughan AT oranda DOT demon DOT co DOT uk> writes:
> "Suhaib M. Siddiqi" wrote:
> > 
> > If I remember correctly; Geoffrey Noer mentioned last month, that it was
> > a Cgywin issue not automake.  Perhaps the problem will be fixed in the
> > next release of Cygwin.
> > 
> > Suhaib
> 
> Yes,  the root of the problem is that 'gcc --print-prog-path=ld' gives a
> win32 path (under cygwin), and I think it is this that the cygwin folks
> plan to fix.

EGCS-1.1.1 (from my site) produce forward slashes, albeit with a drive
specifier. EGCS-1.1.2 will do the same, and the changes are now in the 
dev branch. Does this still pose a problem for libtool (other than the
issue of executable file extensions, which I believe you've fixed
already)?

I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.
The only rationale for using the current scheme is if GCC execs a native 
program, but currently that's not the case and will not be in the near 
foreseeable future.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com