Re: Any problem with chinhook beta repo?
ext Santtu Lakkala wrote: Please do note that I use the old debian devkit on purpose, because the goal in my blog post is to be able to compile the same source for different targets, so there cannot anyway be anything using the new features of the newer devkit. I have to admit that I did not read the whole blog post, I just quickly looked at the chinook target setup :) The debian-etch devkit does not really have new features as such, just updated versions of the tools. Just as an example, the debhelper has been updated and you might not be able to build a package that use compat level 5, which is not supported by the debian-sarge devkit. Also, I have tested each of the commands and they produce a working target, with no arm/armel mismatch. Unfortunately I don't know why is there a problam for Luca. My instructions do use the qemu-0.8.2-sb2 and use the maemo3-debian. It might be that debian-sarge without maemo3-debian breaks things. Yes your instructions have the correct qemu version, but Luca's post revealed that he was using the 0.8.1 version. I hope the final SDK released fixed any problems Luca had. Cheers, Juha -- Juha Kallioinen JID: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Any problem with chinhook beta repo?
Yes your instructions have the correct qemu version, but Luca's post revealed that he was using the 0.8.1 version. I hope the final SDK released fixed any problems Luca had. Cheers, Juha -- Juha Kallioinen JID: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Thanks Juha, yes, I used the installer script for the final SDK and now it works. Previously I tried to upgrade the qemu devkit to the correct version, but it didn't fix my problem, so I used the installer script! Luca Donaggio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Any problem with chinhook beta repo?
Hi, ext Luca Donaggio wrote: On Nov 8, 2007 4:04 PM, Gabriel Schulhof [EMAIL PROTECTED] wrote: On Thu, 2007-11-08 at 15:14 +0100, ext Luca Donaggio wrote: It seems that my sbox target is somewhat misconfigured: it should look in binary-armel subdir on repository.maemo.org, not binary-arm, but I don't have any clue why it happened and how to correct it! IIRC, there is a certain combination of scratchbox parameters (especially the emulation and/or debkits) that results in the package management system thinking that it's on arm rather than armel. I believe the fix is to use the correct emulation and/or debkits. Any clue about how to fix it? I followed these instructions to set up my sbox environment: http://inz.fi/blog/2007/10/22/multi-target-development-for-maemo/ My current parameters for chinhook-armel target (via sb-menu - show) are: Compiler: cs2005q3.2-glibc2.5-arm Architecture: arm Sub-architecture: arm C-library:glibc Devkits: cputransp debian doctools perl debian-sarge CPU-transparency: /scratchbox/devkits/cputransp/bin/qemu-arm-0.8.1-sb2 Apart from the compiler glibc version and debian-sarge among the devkits, they are the same for my bora-armel target, which works just fine (no arm/armel mismatch)! For Chinook debian-sarge should be debian-etch. Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Any problem with chinhook beta repo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juha Kallioinen wrote: ext Luca Donaggio wrote: Any clue about how to fix it? I followed these instructions to set up my sbox environment: http://inz.fi/blog/2007/10/22/multi-target-development-for-maemo/ My current parameters for chinhook-armel target (via sb-menu - show) are: Hi Luca, it looks like your target setup is not quite correct. Inz's blog entry is quite new but the information for a chinook target is incorrect. Here's a target setup that works for me: sb-conf st maemo4-arm -c cs2005q3.2-glibc2.5-arm -d cputransp:perl:debian-etch -t qemu-arm-0.8.2-sb2 The most notable differences are that you should use debian-etch devkit (not debian or debian-sarge) and that the qemu version is wrong. Please do note that I use the old debian devkit on purpose, because the goal in my blog post is to be able to compile the same source for different targets, so there cannot anyway be anything using the new features of the newer devkit. Also, I have tested each of the commands and they produce a working target, with no arm/armel mismatch. Unfortunately I don't know why is there a problam for Luca. My instructions do use the qemu-0.8.2-sb2 and use the maemo3-debian. It might be that debian-sarge without maemo3-debian breaks things. The package versions may indeed be the ones to blame, apt-get upgrade (outside scratchbox) might help. - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHNJhBX9Rc0+po4p0RAvVVAJ9EOc22HTL9gIVkj+ifuXOanMDn4gCgsciH kqd2nnTlgzQeJF7fDcDqCt0= =QiEY -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Any problem with chinhook beta repo?
On Thu, 2007-11-08 at 15:14 +0100, ext Luca Donaggio wrote: It seems that my sbox target is somewhat misconfigured: it should look in binary-armel subdir on repository.maemo.org, not binary-arm, but I don't have any clue why it happened and how to correct it! IIRC, there is a certain combination of scratchbox parameters (especially the emulation and/or debkits) that results in the package management system thinking that it's on arm rather than armel. I believe the fix is to use the correct emulation and/or debkits. Gabriel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
