From tplate at blackmesacapital.com  Thu Mar 18 17:40:53 2004
From: tplate at blackmesacapital.com (Tony Plate)
Date: Thu Mar 18 17:41:12 2004
Subject: [Rd] cygwin tar?
In-Reply-To: <lc2i50t6k9q8lgatni7bk82vmms3mcsfp4@4ax.com>
References: <1079515816.3309.10.camel@xena.iarc.fr>
	<Pine.LNX.4.44.0403171229580.2695-100000@gannet.stats>
	<6.0.3.0.2.20040317100647.055ccf00@mailhost.blackmesacapital.com>
	<lc2i50t6k9q8lgatni7bk82vmms3mcsfp4@4ax.com>
Message-ID: <6.0.3.0.2.20040318093508.090adbb8@mailhost.blackmesacapital.com>

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


[Rd] cygwin tar?
Tony Plate