public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@freemail.ru>
To: viper_88 <viper_88@me.com>, cygwin@cygwin.com
Subject: Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
Date: Thu, 17 Nov 2011 18:50:00 -0000	[thread overview]
Message-ID: <785227862.20111117224903@mtu-net.ru> (raw)
In-Reply-To: <32861517.post@talk.nabble.com>

Greetings, viper_88!

> As you can easily see, most of the stuff is missing. It's a bit odd, though,
> since when I look for, say, pcre (which I definitely had installed), I get
> this:

> Searching for installed packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre

> Searching for installable packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre
> pcre-devel

> Hubert@Hubert-PC ~
> $

> pcre is installed already,

I think you need pcre-devel if you're looking to compile stuff that depends on
it...


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 17.11.2011, <22:47>

Sorry for my terrible english...


--
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

  parent reply	other threads:[~2011-11-17 18:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 19:28 viper_88
2011-11-15 20:46 ` Larry Hall (Cygwin)
2011-11-16 19:34   ` viper_88
2011-11-16 20:01     ` marco atzeri
2011-11-17 12:15       ` viper_88
2011-11-17 13:00         ` marco atzeri
2011-11-17 20:34           ` Dave Korn
2011-11-17 20:38             ` Dave Korn
2011-11-17 18:50         ` Andrey Repin [this message]
2011-11-16 20:05     ` Jesse Ziser
2011-11-16 20:41       ` Tim Prince
2011-11-16 20:12     ` Christopher Faylor

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=785227862.20111117224903@mtu-net.ru \
    --to=anrdaemon@freemail.ru \
    --cc=cygwin@cygwin.com \
    --cc=viper_88@me.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).