From: Paul Sokolovsky <pmiscml@gmail.com>
To: Alban J Pearce <alban@mycroft1.plus.com>
Cc: Holger Freyther <freyther@gmx.net>,
opie-devel@handhelds.org,
Using the OpenEmbedded metadata to build Linux Distributions
<openembedded-devel@lists.openembedded.org>
Subject: Re: Angstrom cannot buile portabase
Date: Sun, 14 Jan 2007 11:55:02 +0200 [thread overview]
Message-ID: <1754192865.20070114115502@gmail.com> (raw)
In-Reply-To: <200701132239.31919.alban@mycroft1.plus.com>
Hello Alban,
Sunday, January 14, 2007, 12:39:31 AM, you wrote:
> I have installed Angstrom
> bitbake , nano works
[]
> NOTE: Applying patch 'kernel-keymap.patch'
[]
> |+++ qt-2.3.10-snapshot-20060120/src/kernel/qkeyboard_qws.cpp 2006-01-20
> 21:16:25.412761096 +0100
> --------------------------
> No file to patch. Skipping patch.
> 19 out of 19 hunks ignored
[]
This patch was done for inconsistent -pN param, I fixed it now, and
checked that it applies and builds.
At the same time, there're ongoing changes for OPIE in OE.dev, so if
you want to just build apps for your production handheld, OpenZaurus
branch is recommended.
Otherwise, we'd need Zaurus people to test OPIE changes in OE.dev,
so your help is appreciated, but expect some breakage then. My general
approach to solve current OPIE issues is to reduce machine
discrepancies in its build to zero, set common requirements for a
machine to be supported in OPIE (adhering to which will automatically
mean that machine is supported) and re-review every patch to QT/E for
unavoidability of application in the current situation (that one being
the situation that original OPIE maintainers no longer have
interest/resources to maintain it).
In this regard, kernel-keymap.patch is in gray area - it currently
being applied inconsistently without even clear major platform
distinction (currently it is applied to Zauruses and Jornada
PocketPC's). So it should be re-evaluated for benefits it offer vs
possible requirements it has and maintenance burden, and either being
applied consistently for all machines, or dropped.
I wanted to discuss these issues with Holger (zecke) (and other core
OPIE folks who'd have time/interest) on IRC first, but now that this
issue was raised, I dump this "seed" message here...
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-01-14 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 19:43 Gtk+ 2.6.10 w/ newer Glibs Michael 'Mickey' Lauer
2007-01-12 20:25 ` Koen Kooi
2007-01-13 0:13 ` Michael 'Mickey' Lauer
2007-01-13 9:52 ` Richard Purdie
2007-01-13 16:15 ` Koen Kooi
[not found] ` <200701132239.31919.alban@mycroft1.plus.com>
2007-01-13 23:35 ` Angstrom cannot buile portabase Holger Freyther
2007-01-14 0:12 ` Koen Kooi
2007-01-14 9:15 ` GoXbox Live
2007-01-14 10:16 ` Koen Kooi
2007-01-14 10:42 ` GoXbox Live
2007-01-14 9:55 ` Paul Sokolovsky [this message]
2007-01-25 23:24 ` Gtk+ 2.6.10 w/ newer Glibs Michael 'Mickey' Lauer
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=1754192865.20070114115502@gmail.com \
--to=pmiscml@gmail.com \
--cc=alban@mycroft1.plus.com \
--cc=freyther@gmx.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=opie-devel@handhelds.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.