Comments on: Multi-target development for maemo

By: Marius Gedminas

Marius Gedminas — Fri, 09 Oct 2009 22:55:24 +0000

Any plans for updating this with a Maemo 5 target? Pretty please?

By: XTL

XTL — Mon, 16 Jun 2008 11:26:46 +0000

I prefer to use tee when having to write to files with root perms from sudo:

echo “…” | sudo tee -a /appendee/file

no rootshell, no redirection and you happen to also see what went into the file. And you can generate the text as non-root.

By: Hendrik Boom

Hendrik Boom — Fri, 30 May 2008 02:45:30 +0000

Well, I got as far as starting the rootstrap creation. The first command seemed to run; the second complained I wasn’t a scratchbox user. This is presumably related to the fact that it didn’t ask me for users to add to scratchbox.

How do I go about adding myself to scratchbox at this point? Or is something else likely to be wrong?

I did get a lot further with this set of instructions than any of the “easy” or “preferred” instructions, by the way.

– hendrik

By: Marius Gedminas

Marius Gedminas — Mon, 17 Dec 2007 22:07:20 +0000

FWIW your instructions don’t work as written; you also need to apt-get install scratchbox-devkit-perl if you want to mention it among the other devkits.

By: Graham Cobb

Graham Cobb — Thu, 15 Nov 2007 18:41:03 +0000

I found that in order to create a working Bora target (in which I could install tools like intl and autoconf) I had to:

1) Leave off the “-c” from the “sb-conf in bora-armel” command, and

2) Edit /etc/apt/sources.list to change the references to “bora” to be to “maemo3.0″. It seems that “bora” is now 3.2 and mixing that up with the 3.0 rootstrap breaks things. In any case, like Inz, I want to build packages that work on 3.* so I want to build against 3.0.

By: Neil Jerram

Neil Jerram — Tue, 13 Nov 2007 23:21:12 +0000

For me the “fakeroot apt-get -f install” step (for bora-armel) does not succeed. Here is the output that I get when running “fakeroot apt-get -f install” again (so as to omit all the installs and upgrades that _do_ succeed):
[sbox-bora-armel: ~] > fakeroot apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done 0 upgraded, 0 newly installed, 0 to remove and 93 not upgraded. 4 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up libpango1.0-common (1.8.1-1osso20) ... You don't have modules directory for version 1.4.0. Use default version instead. Updating the modules list for Pango-1.4.0...find: /usr/lib/pango/1.4.0/modules: No such file or directory /usr/sbin/update-pango-modules: line 20: /usr/bin/pango-querymodules: cannot execute binary file dpkg: error processing libpango1.0-common (--configure): subprocess post-installation script returned error exit status 126 Setting up libgtk2.0-bin (2.6.10-2.osso30) ... Updating the IM modules list for GTK+-2.4.0.../usr/sbin/update-gtk-immodules: line 22: /usr/bin/gtk-query-immodules-2.0: cannot execute binary file dpkg: error processing libgtk2.0-bin (--configure): subprocess post-installation script returned error exit status 126 dpkg: dependency problems prevent configuration of libgtk2.0-0: libgtk2.0-0 depends on libgtk2.0-bin (>= 2:2.6.10-2.osso30); however: Package libgtk2.0-bin is not configured yet. dpkg: error processing libgtk2.0-0 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libgtk2.0-dev: libgtk2.0-dev depends on libgtk2.0-0 (= 2:2.6.10-2.osso30); however: Package libgtk2.0-0 is not configured yet. dpkg: error processing libgtk2.0-dev (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libpango1.0-common libgtk2.0-bin libgtk2.0-0 libgtk2.0-dev E: Sub-process /scratchbox/devkits/debian-sarge/bin/dpkg returned an error code (1)
The root problem seems to be /usr/bin/gtk-query-immodules not being executable. Any idea why that is?

Thanks
- Neil

By: inz

inz — Sat, 27 Oct 2007 20:40:49 +0000

I’m not sure of what debian-devkit chinook should use, but it’s not that big of a deal anyway. Debian-etch would provide a bit newer debian utils, but as the point of this post was to allow development on all versions of maemo, there’s no need for newer ones.

I’m not sure of the C library either. I’ve experienced it to both cause and solve problems, but both cases are rare.

And about upgrading to 3.2 (or to 3.1), at least I like to support all 3.x with single binary. 3.1 and 3.2 might be able to build binaries that work on 3.0, but then again, they might not, so I’m playing it safe.

By: Tom Swindell

Tom Swindell — Sat, 27 Oct 2007 16:28:38 +0000

Should not chinook use debian-etch and no maemo3-debian instead of debian-sarge and maemo3-debian? Also isn’t -c (C library) wrong for all targets? Might also be a good idea to add 3.1 to 3.2 upgrading ‘fakeroot apt-get -f dist-upgrade’. Nice post though, was a great help

By: inz

inz — Mon, 22 Oct 2007 12:59:40 +0000

Well, I think it’s the easy way, but whatever.

By: VRe

VRe — Mon, 22 Oct 2007 12:38:22 +0000

Nice to know that there is somebody else doing it the hard way