From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: any ETA on a fixed xterm-207?
Date: Sun, 8 Nov 2009 06:58:55 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911080653060.13874@localhost> (raw)
i realize i've mentioned this at least a couple times before (on the
angstrom list) but is there any ETA on fixing the unbuildable
xterm-207 package so that i can bitbake beagleboard-demo-image?
the problem with xterm_207 appears to be obvious. the install
script contained therein -- sinstall.sh -- contains the following
snippet:
=====
case ".$cf_mode" in #(vi
.???s??s*) #(vi
PROG_SUID=4000
PROG_SGID=2000
;;
.???s*) #(vi
PROG_SUID=4000
PROG_GRP=
;;
.??????s*)
PROG_SGID=2000
PROG_USR=
;;
esac
PROG_MODE=`echo ".$cf_mode" | sed -e 's/^..//' -e 's/rw./7/g' -e 's/r-./5/g' -e 's/--[sxt]/1/g'`
=====
it seems clear that the point of that snippet is to convert a
symbolic mode to a numeric mode. unfortunately, these days, the
symbolic mode has a trailing period, whereupon the resulting numeric
mode *also* has a trailing period, at which point the subsequent
"chmod" command tries to use a mode of "755." and chokes.
as a quick hack, i snuck in the line:
PROG_MODE=${PROG_MODE%\.}
right after that last line to knock off the trailing period and that
fixed things and allowed xterm to build. a cleaner solution would be
to perhaps whack off that period at the top. either way would work.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-11-08 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 11:58 Robert P. J. Day [this message]
2009-11-08 13:12 ` any ETA on a fixed xterm-207? Philip Balister
2009-11-08 13:16 ` Robert P. J. Day
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=alpine.LFD.2.00.0911080653060.13874@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
/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.