From: Michael J. Hammel <buildroot@graphics-muse.org>
To: buildroot@busybox.net
Subject: [Buildroot] xterm vs rxvt
Date: Sun, 10 Apr 2011 20:12:06 -0600 [thread overview]
Message-ID: <1302487926.6468.13.camel@kepler.graphics-muse.org> (raw)
I noticed rxvt was pulled back in June last year. I've been trying to
get xterm running with 2011.02. It builds okay but fails to run. I've
applied two patches that showed up since 2011.02 was released but that
hasn't helped. The best info I can get so far is that there is a malloc
failure. I have a hunch it might be a problem with network
configuration (only loopback is enabled) and/or missing or improperly
created authorization files, but was not able to narrow it down. Strace
didn't tell me much.
rxvt, on the other hand, builds and runs just fine. I can find no
problems with it yet. I have a package and patch to put it back in if
anyone wants it. I was about to post an enhancement request when I
noticed it had already been pulled once before.
I know its old and not actively maintained, but is there something
specific about why rxvt is considered buggy?
http://git.buildroot.net/buildroot/commit/?id=bb43b2408696787ad90450c9417a2114bbf3949b
--
Michael J. Hammel <buildroot@graphics-muse.org>
reply other threads:[~2011-04-11 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1302487926.6468.13.camel@kepler.graphics-muse.org \
--to=buildroot@graphics-muse.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.