public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: cygport and C:\Windows\system32\tar.exe
Date: Sun, 30 Jun 2019 07:01:00 -0000	[thread overview]
Message-ID: <58004f6c-2789-041d-8e75-65e602748db1@t-online.de> (raw)
In-Reply-To: <bae0be8b-310d-e187-e8f7-f08d3495ce1c@gmail.com>

Am 30.06.2019 um 07:37 schrieb Federico Kircheis:

> My problem is that cyport tries to invoke tar with an absolute file, and
> of course C:\Windows\system32\tar.exe does not understand a path that
> begins with `/cygdrive/c`.

No.  Your problem is that you're trying to use cygport from the wrong
place, causing the PATH seen by it to be completely wrong.  Well, either
that, or that you somehow failed to install Cygwin's own tar, even
though it's part of the base system, so it should always be installed.

Cygport, like many of the more involved utilities delivered by Cygwin,
is meant to be used from inside the Cygwin shell.  At the very least,
you have to ensure that the PATH of the shell running cygport is set up
properly, with Cygwin's `/bin' and/or `usr/bin' mounts at the front of it.
> How do you generally solve that problem?

Basically by not even having it in the first place.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-06-30  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190630053803epcas5p1a61a06ab1cf93b94e3342bf69761f15e@epcas5p1.samsung.com>
2019-06-30  5:37 ` Federico Kircheis
2019-06-30  7:01   ` Hans-Bernhard Bröker [this message]
2019-06-30  7:24     ` Federico Kircheis
2019-06-30  8:20       ` Andrey Repin
2019-07-01 10:43   ` Pavel Fedin

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=58004f6c-2789-041d-8e75-65e602748db1@t-online.de \
    --to=hbbroeker@t-online.de \
    --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).