[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: paths on mingw
From: |
Bernard Dautrevaux |
Subject: |
RE: paths on mingw |
Date: |
Thu, 2 Aug 2001 11:13:34 +0200 |
> -----Original Message-----
> From: Tim Van Holder [mailto:address@hidden
> Sent: Wednesday, August 01, 2001 9:23 PM
> To: stefan
> Cc: address@hidden
> Subject: Re: paths on mingw
>
>
> > Cygwin bash does not care and "a mingw-compiled bash" is
> impossible since
> > there's no fork(). It is also because mingw never wanted to
> be a posix
> > emulation layer.
>
> The lack of fork just makes it slightly more challenging
> (DJGPP also has no
> fork(), but has a fully functional bash). But I see your point.
>
> I suppose libtool could include such a transformation (it's
> easy enough:
> something like "sed s,/cygdrive/\(.\)/,\1:/,g" should do).
As this is only needed when host=cygwin target!=cygwin, this can be in this
case replaced by the more appropriate cygwin-specific invokation:
cygpath -w $path
> So please either
> submit a patch, or point out the specific places where such a
> change would
> be required. I'm surprised this doesn't cause problems for configure
> scripts as well.
>
Probably because configure scripts only call cygwin-provided tools, that
understand cygwin paths; remember these scripts are *meant* to be portable
:-)
HTH
Bernard
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: address@hidden
address@hidden
--------------------------------------------
- paths on mingw, stefan, 2001/08/01
- RE: paths on mingw,
Bernard Dautrevaux <=