Re: [Rd] cygwin tar?
Duncan, thanks for the explanation. I prefer bash to the Windows command
line and it sounds like others do too.
Should I take it then that following the instructions in
src/gnuwin32/INSTALL should allow one to use the .exe's from tools.zip
inside a cygwin bash shell? Following those instructions used to work for
me, but it no longer does -- I get the cygwin1.dll conflict error no matter
what I do. The only thing that works for me is to remove the cygwin1.dll
that came with tools.zip (and thus use the cygwin1.dll that came with
cygwin.) I wonder if something has changed in either Windows 2000 or in
cygwin that makes cygwin1.dll more persistent than it used to be?
-- Tony Plate
At Wednesday 07:38 PM 3/17/2004, Duncan Murdoch wrote:
On Wed, 17 Mar 2004 15:49:41 -0700, you wrote:
To build R from source in a Windows system, do you 'make' from cygwin bash,
or from a Windows command line prompt?
I currently use Cygwin's bash, but I used to use Win98's command line
prompt. I think they both still work, but the command line prompt is
not being tested much these days.
After reading
src/gnuwin32/{INSTALL,readme,readme.packages} and the rw-FAQ, I strongly
suspect the shell commands in there are are intended to be run from only
the Windows command line prompt. I couldn't find any explicit mention of
which shell to use, but in rw-FAQ and readme.packages, the 'cd' commands
(at least those intended for execution on Windows systems) all use backward
slashes, which implies Windows command line. In src/gnuwin32/INSTALL, the
'cd' commands have forward slashes, which only works with a unix-style
shell, like bash. However I suspect those are typos.
I wouldn't pay too much attention to the direction of the slashes.
The documentation is generally written for the users who use the
standard Windows shell, so backslashes are appropriate, but the
developers mainly use Unix-like shells, so forward slashes are what we
use. In fact, forward slashes work in many places in Windows
(including the Win XP command line prompt).
Duncan Murdoch
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
RE: [Rd] cygwin tar?
Hasn't this to do with the fact that cygwin1.dll (dynamically linked
library) is a shared library and it is loaded into memory in a first
come, first served style? Thus, if you load Cygwin's default
cygwin1.dll by for instance starting a Cygwin shell (or even
background processes) and then try to load Rtools cygwin1.dll, the
latter will complain that there is already a loaded library? Similar,
vice versa.
I haven't done my background research so I do not know the above for
sure, but that is how I think about it. Comments anyone?
Example on WinXP Pro: I start a Cygwin bash shell in one window and
open a MSDOS prompt with the PATH setup such that B.R's Rtools are
used exclusively (details in my email on 2004-03-17 @ 14.28) and then
type 'sh' (starts Rtools/bin/sh - not Cygwin/bin/sh) I get
c:\sh
C:\Progra~1\R\Rtools\sh.exe: *** shared version mismatch detected -
0x75BE006D/0x18A20043.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start-Find/Search facility
and delete all but the most recent version. The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
because the other DLL is already loaded. This does not happen if I do
*not* open the Cygwin shell first. Vice versa: Closing the first one
and Rtools/bin/sh works fine. Now Cygwin/bin/sh fails to start.
To see which cygwin1.dll that is loaded one can run msinfo32.exe,
select Software Environment - Loaded Modules and do View | Refresh.
A standard Cygwin/bin/sh shell will load:
cygwin1 1.5.7-cr-0x9e 1,06 MB (1 109 385 bytes)
2004-02-06 13:46 Red Hat c:\cygwin\bin\cygwin1.dll
whereas a Rtools/bin/sh shell (or R CMD build et al) will load
cygwin 1.3.17 922,82 KB (944 968 bytes)
2004-03-02 18:58 Red Hat c:\progra~1\r\rtools\cygwin1.dll
So Tony, do you have a Cygwin/cygwin1.dll loaded in memory when you
try to use Rtools?
Cheers
Henrik
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony Plate
Sent: den 18 mars 2004 17:41
To: Duncan Murdoch
Cc: [EMAIL PROTECTED]
Subject: Re: [Rd] cygwin tar?
Duncan, thanks for the explanation. I prefer bash to the
Windows command
line and it sounds like others do too.
Should I take it then that following the instructions in
src/gnuwin32/INSTALL should allow one to use the .exe's from
tools.zip
inside a cygwin bash shell? Following those instructions
used to work for
me, but it no longer does -- I get the cygwin1.dll conflict
error no matter
what I do. The only thing that works for me is to remove the
cygwin1.dll
that came with tools.zip (and thus use the cygwin1.dll that came
with
cygwin.) I wonder if something has changed in either Windows
2000 or in
cygwin that makes cygwin1.dll more persistent than it used to be?
-- Tony Plate
At Wednesday 07:38 PM 3/17/2004, Duncan Murdoch wrote:
On Wed, 17 Mar 2004 15:49:41 -0700, you wrote:
To build R from source in a Windows system, do you 'make'
from cygwin
bash, or from a Windows command line prompt?
I currently use Cygwin's bash, but I used to use Win98's
command line
prompt. I think they both still work, but the command line
prompt is
not being tested much these days.
After reading
src/gnuwin32/{INSTALL,readme,readme.packages} and the rw-FAQ, I
strongly suspect the shell commands in there are are
intended to be
run from only the Windows command line prompt. I couldn't
find any
explicit mention of which shell to use, but in rw-FAQ and
readme.packages, the 'cd' commands (at least those intended for
execution on Windows systems) all use backward slashes,
which implies
Windows command line. In src/gnuwin32/INSTALL, the 'cd' commands
have forward slashes, which only works with a unix-style
shell, like
bash. However I suspect those are typos.
I wouldn't pay too much attention to the direction of the
slashes. The
documentation is generally written for the users who use the
standard
Windows shell, so backslashes are appropriate, but the developers
mainly use Unix-like shells, so forward slashes are what we use.
In
fact, forward slashes work in many places in Windows
(including the Win
XP command line prompt).
Duncan Murdoch
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailma n/listinfo/r-devel
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] cygwin tar?
On Thu, 18 Mar 2004 09:40:53 -0700, Tony Plate [EMAIL PROTECTED] wrote : Should I take it then that following the instructions in src/gnuwin32/INSTALL should allow one to use the .exe's from tools.zip inside a cygwin bash shell? Following those instructions used to work for me, but it no longer does -- I get the cygwin1.dll conflict error no matter what I do. The only thing that works for me is to remove the cygwin1.dll that came with tools.zip (and thus use the cygwin1.dll that came with cygwin.) I wonder if something has changed in either Windows 2000 or in cygwin that makes cygwin1.dll more persistent than it used to be? I also remove the cygwin1.dll from the tools directory. A few months ago I had some other errors occurring after a cygwin upgrade; I can't remember what they were. The response I got to a question about it on a Cygwin list was that it was impossible for a newer cygwin1.dll not to work with older programs, since they always maintain compatibility; since I had evidence that this was not true, but not time to try to argue about it, I basically gave up on the problem. Right now I'm using version 1.5.5-1 of the cygwin package; I believe the current one is 1.5.8-1. I'm also using 1.2.2-1 of the cygutils package, and the current one is 1.2.5-1. Since this combination works, I'd rather not upgrade. Duncan Murdoch __ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
RE: [Rd] cygwin tar?
At Thursday 10:41 AM 3/18/2004, Henrik Bengtsson wrote:
[...]
So Tony, do you have a Cygwin/cygwin1.dll loaded in memory when you
try to use Rtools?
Yes, because I'm trying to use the exe's from tools.zip from within a
cygwin bash window (because I find it a pain to use different command lines
for different tasks, and I use cygwin bash for everything else.) As far as
I can remember, this used to work until a few months ago. Now I find I
have to remove the cygwin1.dll that came with tools.zip to get things to
work. It sounds like Duncan has a similar experience.
BTW, thanks for the tip on msinfo32.exe. Curiously, for under Windows
2000, it doesn't show a cygwin1.dll loaded, even though I have a number of
cygwin bash windows running. It shows 'cygintl-1.dll', 'cygintl-2.dll',
'cygiconv2.dll', 'nice.exe', 'cat.exe', and 'sleep.exe' (as well as many
other files not related to cygwin.)
-- Tony Plate
At Thursday 10:41 AM 3/18/2004, Henrik Bengtsson wrote:
Hasn't this to do with the fact that cygwin1.dll (dynamically linked
library) is a shared library and it is loaded into memory in a first
come, first served style? Thus, if you load Cygwin's default
cygwin1.dll by for instance starting a Cygwin shell (or even
background processes) and then try to load Rtools cygwin1.dll, the
latter will complain that there is already a loaded library? Similar,
vice versa.
I haven't done my background research so I do not know the above for
sure, but that is how I think about it. Comments anyone?
Example on WinXP Pro: I start a Cygwin bash shell in one window and
open a MSDOS prompt with the PATH setup such that B.R's Rtools are
used exclusively (details in my email on 2004-03-17 @ 14.28) and then
type 'sh' (starts Rtools/bin/sh - not Cygwin/bin/sh) I get
c:\sh
C:\Progra~1\R\Rtools\sh.exe: *** shared version mismatch detected -
0x75BE006D/0x18A20043.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start-Find/Search facility
and delete all but the most recent version. The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
because the other DLL is already loaded. This does not happen if I do
*not* open the Cygwin shell first. Vice versa: Closing the first one
and Rtools/bin/sh works fine. Now Cygwin/bin/sh fails to start.
To see which cygwin1.dll that is loaded one can run msinfo32.exe,
select Software Environment - Loaded Modules and do View | Refresh.
A standard Cygwin/bin/sh shell will load:
cygwin1 1.5.7-cr-0x9e 1,06 MB (1 109 385 bytes)
2004-02-06 13:46 Red Hat c:\cygwin\bin\cygwin1.dll
whereas a Rtools/bin/sh shell (or R CMD build et al) will load
cygwin 1.3.17 922,82 KB (944 968 bytes)
2004-03-02 18:58 Red Hat c:\progra~1\r\rtools\cygwin1.dll
So Tony, do you have a Cygwin/cygwin1.dll loaded in memory when you
try to use Rtools?
Cheers
Henrik
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony Plate
Sent: den 18 mars 2004 17:41
To: Duncan Murdoch
Cc: [EMAIL PROTECTED]
Subject: Re: [Rd] cygwin tar?
Duncan, thanks for the explanation. I prefer bash to the
Windows command
line and it sounds like others do too.
Should I take it then that following the instructions in
src/gnuwin32/INSTALL should allow one to use the .exe's from
tools.zip
inside a cygwin bash shell? Following those instructions
used to work for
me, but it no longer does -- I get the cygwin1.dll conflict
error no matter
what I do. The only thing that works for me is to remove the
cygwin1.dll
that came with tools.zip (and thus use the cygwin1.dll that came
with
cygwin.) I wonder if something has changed in either Windows
2000 or in
cygwin that makes cygwin1.dll more persistent than it used to be?
-- Tony Plate
At Wednesday 07:38 PM 3/17/2004, Duncan Murdoch wrote:
On Wed, 17 Mar 2004 15:49:41 -0700, you wrote:
To build R from source in a Windows system, do you 'make'
from cygwin
bash, or from a Windows command line prompt?
I currently use Cygwin's bash, but I used to use Win98's
command line
prompt. I think they both still work, but the command line
prompt is
not being tested much these days.
After reading
src/gnuwin32/{INSTALL,readme,readme.packages} and the rw-FAQ, I
strongly suspect the shell commands in there are are
intended to be
run from only the Windows command line prompt. I couldn't
find any
explicit mention of which shell to use, but in rw-FAQ and
readme.packages, the 'cd' commands (at least those intended for
execution on Windows systems) all use backward slashes,
which implies
Windows command line. In src/gnuwin32/INSTALL, the 'cd' commands
have forward slashes, which only works with a unix-style
shell, like
bash. However I suspect those are typos.
I wouldn't pay too much attention to the direction of the
slashes. The
documentation
Re: [Rd] cygwin tar?
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.
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
Cygwin and Rtools (Was: RE: [Rd] cygwin tar?)
If it helps anyone, below is the startup script I use in WinXP to get
an MSDOS prompt that give me access to R and Ripley's Rtools so that I
can run RCMD build etc without problems and at the same time keep my
Cygwin installation. This is pretty much what Ripley suggest. Note the
NOTE: ... below!
I'm sorry if mine or your email client cuts the lines.
Henrik Bengtsson
-
Begin: RCMDprompt.bat
-
@echo off
rem
##
rem # Usage: RCMDprompt.bat [path]
rem #
rem # This script opens a MS-DOS prompt with a enviroment variables
rem # set such that R can be ran and packages can be build.
rem # If 'path' is given, the working directory will be set
accordingly.
rem #
rem # NOTE: This scripts works even if Cygwin is installed. HOWEVER,
you
rem # can not have any Cygwin applications running (not even a shell
or
rem # XEmacs for Cygwin) at the same time you try to run RCMD.
rem #
rem # Requires:
rem # To build and install packages two things must be installed, i.e.
rem # exists in the PATH. First, the Rtools compilation [1] by B.
Ripley
rem # must exists. The path (R_TOOLS) to it is set below. Second, Perl
rem # (must not be Cygwin/Perl) must also exists. The path to it is
set
rem # below.
rem #
rem # Reference:
rem # [1] http://www.stats.ox.ac.uk/pub/Rtools/
rem #
rem # Henrik Bengtsson, [EMAIL PROTECTED], March 2004.
rem
##
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # 1. Global environment variables
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # Short version of PROGRAMFILES, e.g. 'C:\Progra~1' instead of
rem # 'C:\Program Files\', which contains spaces that are BAD for R
Co.
set PROGRAMFILES_SHORT=C:\Progra~1
rem # Directory where user directories are
set USERSDIR=C:\users
rem # Set the main R directory
set R_ROOT=%PROGRAMFILES_SHORT%\R
rem # Set the R_HOME directory
set R_HOME=%R_ROOT%\rw1081
rem set R_HOME=%R_ROOT%\rw1090alpha
rem # Set the HOME directory. This is the directory where R looks
rem # for the .Rprofile and .Renviron files. See ?Startup.
set HOME=%USERSDIR%\%USERNAME%\
rem # Set TMPDIR to a temporary directory
set TMPDIR=%TEMP%
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # 2. Setup the PATH
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # Clear the PATH (making the main Cygwin installation invisible)
path ;
rem # Set the LaTeX directory
rem # http://www.miktex.org/
path %PROGRAMFILES%\MikTeX\miktex\bin;%PATH%
rem # Set the Microsoft HTML Help Compiler directory
rem #
http://msdn.microsoft.com/library/tools/htmlhelp/chm/HH1Start.htm
path %PROGRAMFILES%\HTML Help Workshop;%PATH%
rem # Set the Perl directory
rem # http://www.activestate.com/Products/ActivePerl/Download.html
path C:\Perl\bin;%PATH%
rem # Set the Rtools [1] directory
rem # http://www.stats.ox.ac.uk/pub/Rtools/
path %R_ROOT%\Rtools;%PATH%
rem # Set the R_HOME directory
path %R_HOME%\bin;%PATH%
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # 3. Start the MSDOS prompt in the given directory
rem # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
rem # Change directory according to argument 1
cd %1%
rem # Start the MSDOS commando prompt
%SystemRoot%\system32\cmd.exe
-
End: RCMDprompt.bat
-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Prof
Brian Ripley
Sent: den 17 mars 2004 13:40
To: Martyn Plummer
Cc: Tony Plate; Jeff D. Hamann; [EMAIL PROTECTED]
Subject: Re: [Rd] cygwin tar?
On Wed, 17 Mar 2004, Martyn Plummer wrote:
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?
It may or it may not. At least some cygwin1.dll's are broken
and cause
tar to malfunction.
I don't uninstall cygwin, but I do ensure that its path is
not mounted,
since if it thinks there is a /bin/cygwin1.dll or
/usr/bin/cygwin1.dll it
complains, even if that is really
C:/packages/usr/bin/cygwin1.dll and not
in your path.
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
Cygwin, MSys and Rtools can be happy together (Was: RE: [Rd] cygwin tar?)
Regarding the troubles reported by others with Cygwin and MSys, I would like to point out to have both installed merrily such that you can - use Cygwin for all 'normal' work inside of rxvt/xterm. - use MSys/MingW for one main purpose: building R packages. For this to work, I use appropriate settings in the /home/$USER/.profile for MSys to set its path (with the required Tools by BDR) and then change directories into the /home/$USER for Cygwin. That gives transparent access to all files, sources, ... and yet as the Cygwin.bat will not have been executed, that session is free (enough) of the Cygwin dll to build the R packages. I could detail this further if it helps. Regards, Dirk -- The relationship between the computed price and reality is as yet unknown. -- From the pac(8) manual page __ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] cygwin tar?
At Wednesday 05:39 AM 3/17/2004, Prof Brian Ripley wrote:
On Wed, 17 Mar 2004, Martyn Plummer wrote:
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?
It may or it may not. At least some cygwin1.dll's are broken and cause
tar to malfunction.
I don't uninstall cygwin, but I do ensure that its path is not mounted,
since if it thinks there is a /bin/cygwin1.dll or /usr/bin/cygwin1.dll it
complains, even if that is really C:/packages/usr/bin/cygwin1.dll and not
in your path.
To build R from source in a Windows system, do you 'make' from cygwin bash,
or from a Windows command line prompt? After reading
src/gnuwin32/{INSTALL,readme,readme.packages} and the rw-FAQ, I strongly
suspect the shell commands in there are are intended to be run from only
the Windows command line prompt. I couldn't find any explicit mention of
which shell to use, but in rw-FAQ and readme.packages, the 'cd' commands
(at least those intended for execution on Windows systems) all use backward
slashes, which implies Windows command line. In src/gnuwin32/INSTALL, the
'cd' commands have forward slashes, which only works with a unix-style
shell, like bash. However I suspect those are typos.
Also, what did you mean by ensure that its path is not mounted? I tried
'umount'ing the various /bin etc directories, but still got the cygwin1.dll
conflict error when trying to run .exe's from R/tools from the cygwin bash
prompt (with no cygwin system directories on my path).
# in cygwin, after doing 'umount' on all the cygwin system directories
$ c:/cygwin/bin/mount
C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system
(binmo
de)
c: on /cygdrive/c type user (textmode,noumount)
e: on /cygdrive/e type user (textmode,noumount)
f: on /cygdrive/f type user (textmode,noumount)
h: on /cygdrive/h type user (textmode,noumount)
$ type -a cygwin1.dll
cygwin1.dll is /cygdrive/c/R/tools/cygwin1.dll
$ echo $PATH
.:/cygdrive/c/R/tools:/cygdrive/c/MinGW/bin:/cygdrive/c/texmf/miktex/bin:/cygdri
ve/c/Perl/bin/cygdrive/c/Program Files/Html Help
Workshop:/cygdrive/c/gstools/gs
/gs7.03/bin:/cygdrive/c/R/rw1080/bin
$ ls
c:\R\tools\ls.exe: *** proc version mismatch detected - 0x1E4C5751/0x8E0899FA.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start-Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
(All this is using a pretty up-to-date cygwin (downloaded in the last month
or so) under Windows 2000).
-- Tony Plate
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] cygwin tar?
On Wed, 17 Mar 2004 15:49:41 -0700, you wrote:
To build R from source in a Windows system, do you 'make' from cygwin bash,
or from a Windows command line prompt?
I currently use Cygwin's bash, but I used to use Win98's command line
prompt. I think they both still work, but the command line prompt is
not being tested much these days.
After reading
src/gnuwin32/{INSTALL,readme,readme.packages} and the rw-FAQ, I strongly
suspect the shell commands in there are are intended to be run from only
the Windows command line prompt. I couldn't find any explicit mention of
which shell to use, but in rw-FAQ and readme.packages, the 'cd' commands
(at least those intended for execution on Windows systems) all use backward
slashes, which implies Windows command line. In src/gnuwin32/INSTALL, the
'cd' commands have forward slashes, which only works with a unix-style
shell, like bash. However I suspect those are typos.
I wouldn't pay too much attention to the direction of the slashes.
The documentation is generally written for the users who use the
standard Windows shell, so backslashes are appropriate, but the
developers mainly use Unix-like shells, so forward slashes are what we
use. In fact, forward slashes work in many places in Windows
(including the Win XP command line prompt).
Duncan Murdoch
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
[Rd] cygwin tar?
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.
---
Jeff D. Hamann
Forest Informatics, Inc.
PO Box 1421
Corvallis, Oregon USA 97339-1421
541-754-1428
[EMAIL PROTECTED]
www.forestinformatics.com
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] cygwin tar?
On Tue, 16 Mar 2004 10:32:56 -0800, Jeff D. Hamann [EMAIL PROTECTED] 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 ... This error has been fixed in the latest build of r-devel. I'm not sure if you'll see the fix in the build downloadable today, but you will by tomorrow. Duncan Murdoch __ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
