David Rothenberger writes:
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their Windows
machines.
These machines have not had any Cygwin installed; they're just bare Windows
machines.
I provided them tar.exe and cygwin1.dll
David Rothenberger's suggestion (that there needs to be an /etc)
seems to fix the problem for me as well.
I'll let my users know and see if everything works for them.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
On Wed, 6 Aug 2003, Jon LaBadie wrote:
On Wed, Aug 06, 2003 at 01:27:11PM -0400, Larry Hall wrote:
Oh, OK. I didn't know that this was a restatement of that problem
(http://cygwin.com/ml/cygwin/2003-07/msg00932.html). Did you try
running tar on the affected systems with strace? Perhaps
I want to allow the users I support to be able to run Cygwin tar on their Windows
machines.
These machines have not had any Cygwin installed; they're just bare Windows machines.
I provided them tar.exe and cygwin1.dll and assumed that with these, they could run
Cygwin tar sucessfully. It
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their Windows
machines.
These machines have not had any Cygwin installed; they're just bare Windows machines.
I provided them tar.exe and cygwin1.dll and assumed that with these, they could run
David Rothenberger wrote:
David Rothenberger writes:
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their
Windows machines.
These machines have not had any Cygwin installed; they're just bare Windows
machines.
I provided
On Fri, Aug 08, 2003 at 09:12:45AM -0700, David Rothenberger wrote:
David Rothenberger wrote:
David Rothenberger writes:
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their
Windows machines.
These machines have not had any Cygwin
Igor Pechtchanski wrote:
Yes, you're quite correct. Cygcheck will only list the DLLs that the
program is statically linked to (that is, it's linked to the import
libraries). If the program uses dlopen() or LoadLibrary() to load the
library (like rxvt does with libX11/libW11), cygcheck will
Message-ID:
[EMAIL PROTECTED]
From: Biederman, Steve [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: What is the minimum needed to run gtar?
Date: Tue, 5 Aug 2003 17:04:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Steve Biederman said:
I
, Steve
Cc: '[EMAIL PROTECTED]'
Subject: Re: What is the minimum needed to run gtar?
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their Windows
machines.
These machines have not had any Cygwin installed; they're just bare Windows machines.
I provided
: Tuesday, August 05, 2003 8:54 PM
To: Biederman, Steve
Cc: '[EMAIL PROTECTED]'
Subject: Re: What is the minimum needed to run gtar?
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on
their Windows machines.
These machines have not had any Cygwin
On Wed, 6 Aug 2003, David A. Case wrote:
On Wed, Aug 06, 2003, David Rothenberger wrote:
You can find out what DLLs an executable needs by running cygcheck on it.
Note that this may not give a complete list. Consider rxvt.exe:
quine% cygcheck rxvt.exe
Found: .\rxvt.exe
Found:
Brian Dessent wrote:
Igor Pechtchanski wrote:
Yes, you're quite correct. Cygcheck will only list the DLLs that the
program is statically linked to (that is, it's linked to the import
libraries). If the program uses dlopen() or LoadLibrary() to load the
library (like rxvt does with
Christopher Faylor writes:
On Fri, Aug 08, 2003 at 09:12:45AM -0700, David Rothenberger wrote:
David Rothenberger wrote:
David Rothenberger writes:
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin tar on their
Windows machines.
On Wed, Aug 06, 2003 at 02:29:44PM -0700, David A. Case wrote:
On Wed, Aug 06, 2003, David Rothenberger wrote:
You can find out what DLLs an executable needs by running cygcheck on it.
Note that this may not give a complete list. Consider rxvt.exe:
quine% cygcheck rxvt.exe
Found: .\rxvt.exe
David A. Case wrote:
On Wed, Aug 06, 2003, David Rothenberger wrote:
You can find out what DLLs an executable needs by running cygcheck on it.
Note that this may not give a complete list. Consider rxvt.exe:
quine% cygcheck rxvt.exe
Found: .\rxvt.exe
Found: C:\cygwin\bin\rxvt.exe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
Of Larry Hall
Biederman, Steve wrote:
I want to allow the users I support to be able to run Cygwin
tar on their Windows machines.
These machines have not had any Cygwin installed; they're just
bare Windows machines.
I provided
On Wed, Aug 06, 2003 at 01:27:11PM -0400, Larry Hall wrote:
Oh, OK. I didn't know that this was a restatement of that problem
(http://cygwin.com/ml/cygwin/2003-07/msg00932.html). Did you try
running tar on the affected systems with strace? Perhaps a comparison
of the output from a machine
On Wed, Aug 06, 2003, David Rothenberger wrote:
You can find out what DLLs an executable needs by running cygcheck on it.
Note that this may not give a complete list. Consider rxvt.exe:
quine% cygcheck rxvt.exe
Found: .\rxvt.exe
Found: C:\cygwin\bin\rxvt.exe
rxvt.exe
.\cygwin1.dll
19 matches
Mail list logo
