From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: getclip and cygutils and cygcheck
Date: Wed, 12 Jun 2013 15:22:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A7021C58055@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A7021C57FB3@USA7109MB022.na.xerox.net>
(Several attempts here. Got my address blocked somehow.
Sorry if duplicates appear. Not my day.)
Sorry for the noise...getclip is in cygutils-extra (duh!),
but the cygcheck error is still interesting maybe.
--KN
-----Original Message-----
The Cygwin Search page...
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=getclip.exe
...indicates that getclip is in cygutils-1.4.12-1 but I've
updated ...
$ cygcheck -c cygutils
Cygwin Package Information
Package Version Status
cygutils 1.4.12-2 OK
$
That explains, maybe, why I don't have getclip anymore since
my recent update:
$ type getclip
-bash: type: getclip: not found
$
I know things got moved around w.r.t. cygutils recently, but
where is getclip?
Generating cygcheck output, I get an error:
$ cygcheck -svr > cygcheck.out.txt
cygcheck: Wrong architecture. Only ix86 executables supported.
$
Attached nonetheless: cygcheck.out.txt
--Ken Nellis
--
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
next prev parent reply other threads:[~2013-06-12 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 14:48 Nellis, Kenneth
2013-06-12 15:22 ` Nellis, Kenneth [this message]
2013-06-12 15:40 ` Corinna Vinschen
2013-06-12 17:57 ` Christopher Faylor
2013-06-12 19:53 ` Thomas Wolff
2013-06-13 9:56 ` Corinna Vinschen
2013-06-13 18:13 ` Jeremy Hetzler
2013-06-14 9:16 ` Corinna Vinschen
2013-06-15 3:15 ` Jeremy Hetzler
2013-06-15 3:36 ` Jeremy Hetzler
2013-06-15 17:45 ` Arthur Tu
2013-06-15 19:36 ` Thomas Wolff
2013-06-17 10:16 ` Corinna Vinschen
2013-06-17 13:13 ` Corinna Vinschen
2013-06-19 17:30 ` Corinna Vinschen
2013-06-19 17:35 ` Jeremy Hetzler
2013-06-19 17:45 ` Corinna Vinschen
2013-06-19 17:11 ` Ken Jackson
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=0D835E9B9CD07F40A48423F80D3B5A7021C58055@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@xerox.com \
--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).