From: Patrick Ohly <Patrick.Ohly@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Maemo compatible toolchain
Date: Tue, 16 Jan 2007 21:58:26 +0100 [thread overview]
Message-ID: <1168981106.3819.28.camel@ip6-localhost> (raw)
In-Reply-To: <1168900952.5860.107.camel@localhost.localdomain>
On Mon, 2007-01-15 at 22:42 +0000, Richard Purdie wrote:
> On Mon, 2007-01-15 at 19:54 +0100, Patrick Ohly wrote:
> > ork on the official image because I want my software to be
> > usable by "normal" users without having to reflash their devices.
> > There's Scratchbox of course, but it currently does not work for me
> > (known incompatibility with 2.6.18 kernel). Is compiling for Maemo
> > with
> > OE something that has been tried before?
>
> As far as toolchains go, poky has a POKYMODE (eabi5) which roughly
> corresponds to maemo's csl 'EABI' toolchain. I think those versions of
> the csl packages were added into OE by me.
Thanks for the pointer, I might try that next. My previous attempts were
not successful enough to get more than the simplest executables running
on the Nokia 770 (generic distro + nokia770 device + a few preferred
versions => glibc-intermediate fails to compile; angstrom-2007.1 +
nokia770 => almost works, but too recent glibc to run a full
SyncEvolution binary on the 770).
As interesting as playing around with OE is, time is up now and I guess
I will just install a suitable kernel and resurrect my Scratchbox
installation to make some progress with my real issue (DBus (?) timeouts
in certain eds-dbus API calls that SyncEvolution depends on).
--
Bye, Patrick Ohly
--
Patrick.Ohly@gmx.de
http://www.estamos.de/
prev parent reply other threads:[~2007-01-16 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 18:54 Maemo compatible toolchain Patrick Ohly
2007-01-15 22:42 ` Richard Purdie
2007-01-16 20:58 ` Patrick Ohly [this message]
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=1168981106.3819.28.camel@ip6-localhost \
--to=patrick.ohly@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox