public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Using cygwin tar from a DOS window
Date: Wed, 2 Sep 2020 20:09:01 +0200	[thread overview]
Message-ID: <104c633d-d3e6-026c-d890-092c791faa7e@towo.net> (raw)
In-Reply-To: <1053b95d-a48b-5b19-c144-907d6912dc75@cs.umass.edu>



Am 02.09.2020 um 19:59 schrieb Eliot Moss:
> On 9/2/2020 1:40 PM, Douglas Coup wrote:
>>
>> On 9/2/2020 1:28 PM, Eliot Moss wrote:
>>> On 9/2/2020 1:00 PM, Douglas Coup wrote:
>>>>
>>>> On 9/2/2020 12:53 PM, Bill Stewart wrote:
>>>>> On Wed, Sep 2, 2020 at 8:58 AM Douglas Coup wrote:
>>>>>
>>>>> But if I use tar from a DOS window ...
>>>>> Surely you don't mean DOS? DOS doesn't exist in Windows any more 
>>>>> (unless
>>>>> you are using an emulator like DosBox or a VM).
>>>>>
>>>>> Do you mean a cmd.exe console window? (cmd.exe is a Windows 
>>>>> console-mode
>>>>> program that, despite appearances, is not "DOS." DOS was a real-mode
>>>>> single-tasking operating system.)
>>>>>
>>>>> Bill
>>>>> -- 
>>>>> Problem reports: https://cygwin.com/problems.html
>>>>> FAQ: https://cygwin.com/faq/
>>>>> Documentation: https://cygwin.com/docs.html
>>>>> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>>>>
>>>> Yes, a cmd.exe console window.
>>>
>>> Hardly the point :-) ...
>>>
>>> But I think your problem may be that the Cygwin dlls need to be on 
>>> the search path,
>>> and you're hoping that none of them have names that are the same as 
>>> ones earlier on
>>> the path ...
>>>
>>> Best - Eliot Moss
>>> -- 
>>> Problem reports: https://cygwin.com/problems.html
>>> FAQ: https://cygwin.com/faq/
>>> Documentation: https://cygwin.com/docs.html
>>> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>>
>> I did try copying all of the .dll files in the Cygwin bin folder to 
>> the same folder where the copy of Cygwin's tar.exe sits. That folder 
>> appears first in the PATH.  But despite that, trying to invoke tar 
>> from the cmd window still pops up the window saying cyggcc_s-1.dll 
>> can't be found.
>
> I meant that your PATH should have the Cygwin bin folder in it, 
> somewhere.  Does that not work for you?  But my setup definitely has 
> the cyggcc_s-1.dll file in /bin and /usr/bin.
> It comes from the libgcc1 package (libgcc1-9.3.0-2 in my case).
Some independent comments:
* I see cyggcc_s-seh-1.dll in the libgcc1 package, not cyggcc_s-1.dll
* My current cygwin tar does not depend on cyggcc_s-1.dll
* Maybe your cygwin tar is an older release, now and then gcc library 
conventions have changed
Thomas

  reply	other threads:[~2020-09-02 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 14:58 Douglas Coup
2020-09-02 16:53 ` Bill Stewart
2020-09-02 17:00   ` Douglas Coup
2020-09-02 17:28     ` Eliot Moss
2020-09-02 17:40       ` Douglas Coup
2020-09-02 17:50         ` Bill Stewart
2020-09-02 17:59         ` Eliot Moss
2020-09-02 18:09           ` Thomas Wolff [this message]
2020-09-02 21:30 ` Wayne Davison
2020-09-02 21:53   ` Bill Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=104c633d-d3e6-026c-d890-092c791faa7e@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).