Re: PGI Compiler patch for cygwin

[Christopher Hulbert]

On 2/24/06, Ralf Wildenhues <address@hidden> wrote:
> * Eric Blake wrote on Fri, Feb 24, 2006 at 02:51:07PM CET:
> > According to Christopher Hulbert on 2/22/2006 5:56 AM:
> > >
> > > Actually it seems the problem is that a unix-style path is passed to
> > > lib as the library name. This is probably not the correct fix, but
> > > what I did was add the following to the func_extract_archives function
> > > between the *-darwin* and * case.
> > >       *-cygwin*)
> > >         my_xdir=`cygpath -m $my_xdir`
> > >         my_xabs=`cygpath -m $my_xabs`
> > >         func_extract_an_archive "$my_xdir" "$my_xabs"
> > >         ;;
> >
> > Missing some proper quoting - consider if my_xabs contained something like
> > '/dir with 2  spaces/file'.  Furthermore, I don't think this should this
> > be done globally for cygwin because it penalizes compilers that do
> > understand POSIX paths (gcc).
>
> Certainly all uses of `cygpath' in ltmain are best replaced with uses of
> the `fix_srcfile_path' variable.

I didn't use that variable because I don't like the -w option.  bash
sometimes strips out the backslahses as was the case when it spit out
the error.  If I recall correctly, the forward slash is an acceptable
file separator in windows these days (except in command.com?),
although it may not be true for all previouse releases of windows. 
Certainly they would have done the same thing though :)!


>  We may need more variables like that,
> to indicate the necessity of fixing for
> - the compiler
> - the archiver
> - maybe even the linker separately from the compiler (hopefully not),
> - possibly the name lister (NM).
>
> Cheers,
> Ralf
>