public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Duncan Roe <duncan_roe@acslink.net.au>
To: cygwin@cygwin.com
Subject: Re: FW: Error installing/updating Cygwin on Windows 10
Date: Sun, 24 Jan 2016 22:52:00 -0000	[thread overview]
Message-ID: <20160124220207.GB6031@dimstar.local.net> (raw)
In-Reply-To: <BLU170-W23A59132F428524EBD61329EC60@phx.gbl>

On Sun, Jan 24, 2016 at 02:30:34PM -0500, Maarten Jacobs wrote:
> Hello,
>
> I have been getting the following error when I update/install packages in Cygwin (32-bit) on Windows 10:
>
> Package: _/Unknown package
> base-files-mketc.sh exit code 1
>
> When I look at /var/log/setup.log.full, it gives me the following cryptic error message:
>
> 2016/01/24 14:21:35 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/base-files-mketc.sh"
> Directory /cygdrive/c/Windows/SysWOW64/drivers/etc does not exist; exiting
> If directory name is garbage you need to update your cygwin package
> 2016/01/24 14:21:35 abnormal exit: exit code=1
>
Hi Martin,

I got that message yesterday. It went away when I created the etc directory
(from an Admin CMD window), suggest you do likewise.

Cheers ... Duncan.

--
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:[~2016-01-24 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BLU170-W2358ECF40AEBE4116058499EC60@phx.gbl>
2016-01-24 22:51 ` Maarten Jacobs
2016-01-24 22:52   ` Duncan Roe [this message]
     [not found]     ` <BLU170-W72425FD134EFE7E1A072399EC60@phx.gbl>
2016-01-24 23:39       ` Duncan Roe
2016-01-25  6:42         ` Larry Hall (Cygwin)
2016-01-25  7:04           ` Maarten Jacobs
2016-01-25  9:10             ` Larry Hall (Cygwin)
2016-01-25 21:00               ` Maarten Jacobs

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=20160124220207.GB6031@dimstar.local.net \
    --to=duncan_roe@acslink.net.au \
    --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).