[maemo-developers] Cmake + Armel + Fremantle = Segfault

From: Nathan Anderson nathan at andersonsplace.net
Date: Thu Oct 15 19:39:39 EEST 2009
According to a set of posts on this mailing list this is a known issue
(http://www.mail-archive.com/maemo-developers@maemo.org/msg20041.html); but
I didn't see a resolution to this.   As more developers start working on
moving packages to the fremantle OS, this is going to crop up more and more.

Can we come to some sort of conclusion on this so that we can get this fixed

The only two solutions I've seen presented are:
1. Putting of a non-arm binary in the extras-devel repository (i.e. a
scratchbox host x86 cmake) so that we can use it as a dependancy.
2. Or the gatekeepers of the builder to add a new cmake to the devkit in the
auto-build environment -- and have this cmake published (in a garage
project?) so that the devs can get it so they can use it locally to test the
compiling of apps on their scratchboxes armel targets.

I think the devkit-cmake (or maybe it should be named scratchbox-cmake) idea
is the simplist to implement -- and doesn't require the build-keepers to do
anything.   Or do we need to create a "new" repository (i.e.
fremantle/scratchbox) so that any other tools we find broken in the future
can be put in their to keep x86 binaries out of the repository.      


More information about the maemo-developers mailing list