public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cannot Execute urxvt after upgrade
Date: Thu, 19 Jul 2012 21:15:00 -0000	[thread overview]
Message-ID: <500878BF.8070507@cygwin.com> (raw)
In-Reply-To: <BLU0-SMTP170955D78AEAA3C3B8B52C6CED90@phx.gbl>

On 7/19/2012 4:42 PM, Aaron Schneider wrote:
> On 19/07/2012 22:30, Larry Hall (Cygwin) wrote:
>> On 7/19/2012 4:15 PM, Aaron Schneider wrote:
>>> On 19/07/2012 22:00, K Stahl wrote:
>>>
>>> I couldn't find any version of urxvt on cygwin's release mirror, so, no
>>> packages to start from.
>>
>> <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=urxvt>
>>
>>> Furthermore, for what you are looking for, isn't
>>> rxvt pretty much the same?
>>>
>>> http://cygwin.com/ml/cygwin/2009-05/msg00078.html
>>
>> Pretty much, minus the unicode support and some other niceties mentioned
>> in the message you quoted above.  Of course, stepping back to rxvt puts you
>> in the realm of dead code.  So if bit-rot is OK with you... ;-)
>>
>
> It results that the package is named rxvt-unicode-X-9.07-1.tar.bz2 but in
> the end install binaries that are named urxvt:
>
> usr/bin/urxvt-X.exe
> usr/bin/urxvtc-X.exe
> usr/bin/urxvtd-X.exe
>
> and all of them were compiled on Jan 2010. The non unicode is even older, so
> probably everything is broken. I get also the "Bad address" or "unable to
> connect to the rxvt-unicode daemon: No such file or directory" errors.

Yes, as Eric pointed out, these packages would need to be updated or the
old perl libraries would need to be restored to make them work again.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?


--
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:[~2012-07-19 21:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 19:15 K Stahl
2012-07-19 19:26 ` K Stahl
2012-07-19 19:40 ` Eric Blake
2012-07-19 20:00   ` K Stahl
2012-07-19 20:16     ` Aaron Schneider
2012-07-19 20:31       ` Larry Hall (Cygwin)
2012-07-19 20:42         ` Aaron Schneider
2012-07-19 21:15           ` Larry Hall (Cygwin) [this message]
2012-07-19 21:45             ` K Stahl
2012-07-20  8:27         ` Corinna Vinschen
2012-07-20 12:13           ` K Stahl
2012-07-20 14:01             ` K Stahl
2012-07-20 22:06             ` Thomas Wolff
2012-07-21 13:51               ` K Stahl
2012-07-22  3:54     ` Charles Wilson
2012-07-23 18:11       ` K Stahl
2012-07-23 18:30         ` marco atzeri
2012-07-23 19:36           ` K Stahl
2012-07-23 19:43             ` marco atzeri
2012-07-23 19:55               ` Aaron Schneider
2012-07-23 20:06                 ` marco atzeri
2012-07-23 20:15                   ` Aaron Schneider
2012-07-23 20:27               ` K Stahl
2012-07-23 20:30                 ` K Stahl
2012-07-24  5:15                   ` marco atzeri
2012-07-24 14:00                     ` 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=500878BF.8070507@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).