[CC'ing the last uploader for the package, according to the debian/changelog]
On Wed, Aug 26, 2009 at 5:12 AM, Graham Cobb<g+...@cobb.uk.net> wrote:
> Cmake is required to build opensync. It works fine on Diablo. However, in
> the Fremantle SDK it is broken (segfault during "Check for working C
> compiler:" step).
> Cmake is not part of the SDK (it should be, but that is another matter). It
> is in extras-devel.
> Does anyone know who packaged cmake? The maintainer field is still set to
> upstream but it has a "maemo" version number. Any volunteers to work out why
> cmake is not working and/or to try repackaging it?
Well, we had the same problem so we produced a modified version that
is built using sbox's host-g++/host-gcc. This allows to use the same
binary both in x86 and ARMEL targets, and is a lot faster on ARMEL
(and does not segfault).
The "catch" is that, given that the binary is actually compiled for
x86, it will not run if installed on the device. It will only work on
So I ask other developers using cmake (I suppose there are not that
many, otherwise the problem would be reported sooner, given that cmake
+ fremantle + ARMEL always segfaults): is it acceptable for you?
Note that this is in fact a qemu bug, but doing the compilation with
host-gcc/host-g++ did the trick and is easier than debugging qemu.
If others agree, I can produce a patch against the latest version in
fremantle-extras devel and upload a new version for cmake.
OpenBossa Labs - INdT
Manaus - Brazil
maemo-developers mailing list