public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: cygcheck and literal plus sign
Date: Sat, 28 Jan 2017 04:01:00 -0000	[thread overview]
Message-ID: <CAJ1FpuMrKniJ7mPi0dqmZERo876q0ow2MExepC_J-D7aGnsVaA@mail.gmail.com> (raw)
In-Reply-To: <588c098a.6a099d0a.bd219.1f24@mx.google.com>

On 27 January 2017 at 20:01, Steven Penny wrote:
> On Mon, 27 Jan 2014 16:43:23, Steven Penny wrote:
>>     $ cygcheck -p 'g\x2b\x2b.exe'
>
> It looks like this is broken again. package-grep does work:
>
> $ q=https://cygwin.com/cgi-bin2/package-grep.cgi
> $ curl -s "$q"'?text=1&arch=x86_64&grep=mingw32-g%2B%2B' | awk 'NR>1{$0=$1}1'
> Found 4 matches for mingw32-g++
> mingw64-i686-gcc-g++-5.4.0-2
> mingw64-i686-gcc-g++-5.4.0-3
> mingw64-x86_64-gcc-g++-5.4.0-2
> mingw64-x86_64-gcc-g++-5.4.0-3
>
> but it seems no incantation will make cygcheck work:

Try this:
$ cygcheck -p "mingw32-g[*-,][*-,]"
Found 4 matches for mingw32-g[*-,][*-,]
mingw64-i686-gcc-g++-5.4.0-2 - mingw64-i686-gcc-g++: GCC for Win32
(i686-w64-mingw32) toolchain (C++) (installed binaries and support
files)
mingw64-i686-gcc-g++-5.4.0-3 - mingw64-i686-gcc-g++: GCC for Win32
(i686-w64-mingw32) toolchain (C++) (installed binaries and support
files)
mingw64-x86_64-gcc-g++-5.4.0-2 - mingw64-x86_64-gcc-g++: GCC for Win64
toolchain (C++) (installed binaries and support files)
mingw64-x86_64-gcc-g++-5.4.0-3 - mingw64-x86_64-gcc-g++: GCC for Win64
toolchain (C++) (installed binaries and support files)

HTH
Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
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:[~2017-01-28  4:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 23:59 Steven Penny
2014-01-22  5:58 ` Christopher Faylor
2014-01-22  6:46   ` Marco Atzeri
2014-01-22 11:35   ` Andrew Schulman
2014-01-22 15:07     ` Christopher Faylor
2014-01-22 16:03       ` Andrew Schulman
2014-01-22 16:06       ` David Boyce
2014-01-22 16:13         ` Larry Hall (Cygwin)
2014-01-25  2:26         ` Steven Penny
2014-01-27 15:48           ` Gates, Roger
2014-01-27 18:59             ` Larry Hall (Cygwin)
2014-01-27 22:43             ` Steven Penny
2017-01-28  3:01               ` Steven Penny
2017-01-28  4:01                 ` Doug Henderson [this message]
2017-01-28 12:21                   ` Steven Penny
2017-01-28 17:45                     ` Brian Inglis
2017-01-28 19:06                       ` Eric Blake
2017-01-28 19:59                         ` Brian Inglis
2017-01-30 18:30                 ` Jon Turney
2017-01-31  0:00                   ` Steven Penny

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=CAJ1FpuMrKniJ7mPi0dqmZERo876q0ow2MExepC_J-D7aGnsVaA@mail.gmail.com \
    --to=djndnbvg@gmail.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).