[Rd] cygwin tar?

[Martyn Plummer]

I had the same problem as Tony with multiple copies of cygwin1.dll. But
doesn't this solution (renaming cygwin1.dll in the tools directory) just
link the tools with the cygwin1.dll that comes with cygwin? In which
case will it work if the tools are linked against a different version of
the cygwin1 library? 

To answer Jeff's question
> 
>  if($WINDOWS) {
>      ## workaround for paths in Cygwin tar
>      $filepath =~ s+^([A-Za-x]):+/cygdrive/\1+;
>  }
> 
> in the build script and don't think it needs to be there since you can
> use the tar utility that comes with mingw, yes?

You're talking about the tar that comes with MSYS. And no you can't use
it because it can't handle symbolic links, a problem that is discussed
in the documentation.

On Tue, 2004-03-16 at 20:23, Tony Plate wrote:
> Jeff: alternatively, I don't think it's necessary to completely remove a 
> cygwin installation in order to use MinGW and build R.
> 
> What I have done to build R from a bash cygwin window under Windows 2000:
> 
> (1) put the "tools" directory and the MinGW directories ahead of any cygwin 
> directories on the path
> (2) rename the cygwin1.dll that was in the "tools" directory (from Brian 
> Ripley's tools.zip) to something like "Xcygwin1.dll" (to avoid cygwin 
> conflicts)
> 
> I also have ActiveState Perl installed and ahead of the cygwin perl on the 
> path (though I have a wrapper for it that translates cygwin paths on the 
> command line to windows paths).
> 
> This configuration is different from the instructions in 
> src/gnuwin32/INSTALL in that I don't use the cygwin1.dll from 
> tools.zip.  However, since updating some things recently, having 
> cygwin1.dll in the tools directory always resulted in the "cygwin1.dll 
> conflict" error, even when I changed the PATH to not have any other version 
> of cygwin1.dll on it.
> 
> This may or may not work for anyone else, but it seems to be working for me 
> at the moment: I can build R and the recommended packages from source and 
> run the tests.
> 
> -- Tony Plate
> 
> At Tuesday 11:32 AM 3/16/2004, Jeff D. Hamann wrote:
> >I've been attempting to create a new R package and recently removed the
> >cygwin installation from my machine since R requires the use of the MingW
> >tools for building an R package with C code. However, when I tried to build
> >a source package, I found the following results:
> >
> >
> >* removing junk files
> >* building 'Rconifers_0.7-1.tar.gz'
> >tar: /cygdrive/C/usfs/psw_redding/software/current/Rconifers_0.7-1.tar:
> >Cannot open: No such file or directory
> >tar: Error is not recoverable: exiting now
> >tar: /cygdrive/C/usfs/psw_redding/software/current/Rconifers_0.7-1.tar:
> >Cannot open: No such file or directory
> >tar: Error is not recoverable: exiting now
> >tar: /cygdrive/C/usfs/psw_redding/software/current/Rconifers_0.7-1.tar:
> >Cannot open: No such file or directory
> >tar: Error is not recoverable: exiting now
> >Rconifers_0.7-1.tar: No such file or directory
> >
> >
> >C:\usfs\psw_redding\software\current>
> >
> >which looks like the cygwin path is hard coded into the build script for the
> >rcmd. I found the
> >
> >  if($WINDOWS) {
> >      ## workaround for paths in Cygwin tar
> >      $filepath =~ s+^([A-Za-x]):+/cygdrive/\1+;
> >  }
> >
> >in the build script and don't think it needs to be there since you can use
> >the tar utility that comes with mingw, yes? I replaced the previous chunk of
> >code with:
> >
> >  if($WINDOWS) {
> >      ## workaround for paths in Cygwin tar
> >      $filepath =~ s+^([A-Za-x]):+/\1+;
> >  }
> >
> >which has solved the problem. I just don't know how to get this into the
> >latest build or release of R?
> >
> >Jeff.