From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: any ETA on a fixed xterm-207?
Date: Sun, 08 Nov 2009 13:12:07 +0000 [thread overview]
Message-ID: <4AF6C3A7.3020102@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911080653060.13874@localhost>
On 11/08/2009 11:58 AM, Robert P. J. Day wrote:
>
> 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?
I can reproduce the problem, but I cannot implement a fix and test until
Tuesday AM at the earliest.
Philip
>
> 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
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-11-08 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 11:58 any ETA on a fixed xterm-207? Robert P. J. Day
2009-11-08 13:12 ` Philip Balister [this message]
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=4AF6C3A7.3020102@balister.org \
--to=philip@balister.org \
--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.