hanks again for your time.
-Original Message-
From: David Rothenberger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 2:06 PM
To: Biederman, Steve
Cc: '[EMAIL PROTECTED]'
Subject: tar and remote machines (was RE: What is the minimum needed to
run gtar?)
> What is the correct solution to this problem?
Is the correct solution to invoke tar with the "--force-local" option?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
(Resuming an earlier discussion ...)
In my Cygwin environment, I can invoke tar with Windows-style pathnames,
i.e, "tar -cf C:/temp/foo.tar ." My non-Cygwin users can't; for them, the
"C:" is interpreted as a remote machine name and they get "cannot execute
remote shell".
What is the correct so
nstalled a Cygwin build environment in order to debug the problem,
the problem disappeared. But its easily reproduced on a bare Windows machine.
-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 8:54 PM
To: Biederman, Steve
Cc: '[EMAIL PROTECTE
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 appear
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
Docume
Attached is a gzipped strace from the failing machine.
The strace stops at that point; no further output,
though tar continues to consume CPU time.
-Original Message-
From: Larry Hall
To: Biederman, Steve
Cc: '[EMAIL PROTECTED]'
Sent: 8/6/2003 10:27 AM
Subject: Re: W
I'm trying to build tar. I run ./configure CFLAGS=-g. It appears to run
to completion. But then when I try to make, I get:
make: makefile: line 15: Error -- Expecting macro or rule defn, found neither
What's wrong?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem r
When I attempt to run configure, I get:
$ ./configure CFLAGS=-g
configure: loading cache /dev/null
.: ./configure 1126: /dev/null: not found
-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 12:13 PM
To: Biederman, Steve
Found it.
-Original Message-
From: Biederman, Steve
Sent: Thursday, July 17, 2003 1:40 PM
To: '[EMAIL PROTECTED]'
Subject: RE: tar 1.13.25 runs forever and produces nothing on this test
ca se
> You'll also want the source for tar. Get that from setup too.
I don&
> You'll also want the source for tar. Get that from setup too.
I don't see where I have a choice within setup for source ...
-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 12:13 PM
To: Biederman, Steve
Cc: '[EMAIL PROTE
Which I've never done; I'm not a cygwin developer, just a user.
Do you remember where cygwin documents how to set up a build environment
and get a build going?
-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 11:00 AM
To: Biederman
Any suggestions how I can proceed to debug why tar acts the way it does for me and
not for you?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http:
tar 1.13.25 runs forever, consuming CPU time, and produces nothing, on the following
test case:
Go to an empty directory. Extract the attached with "tar -xzf hang.tgz".
Test that tar works on the extracted tree by doing something like "tar -cf
/temp/test.tar ."
Now, "mv ATA_INTERFAC ATA_INTERF
14 matches
Mail list logo
