Re: Maemo SDK scratchbox breaks with Debian lenny upgrade
On Sunday 10 August 2008 18:11:58 Graham Cobb wrote: > I use UML on another system and it is a good compromise. It achieves near > native speed. My only problem is creating a reliable UML kernel. I am > hopeful I will eventually succeed! In case anyone else hits this problem of using scratchbox on a Debian lenny 64-bit system, I have got a workround. I have a UML 32-bit kernel which seems to run on AMD64 (with latest lenny AMD64 kernel) and which supports building using scratchbox. I have created a debian package for it (derived from the standard user-mode-linux package) which you can download from: http://www.cobb.uk.net/NokiaIT/uml-maemo_2.6.25-1um-2maemo1_i386.deb sources: http://www.cobb.uk.net/NokiaIT/uml-maemo_2.6.25-1um-2maemo1.tar.gz This installs on i386 but to install it on amd64 you have to force it: dpkg --force-architecture -i uml-maemo_2.6.25-1um-2maemo1_i386.deb To run the kernel, use /usr/bin/linux.uml.maemo. Note that the kernel version number ends in -maemo-32 so that the modules (in /usr/lib/uml/modules) do not conflict with the standard user-mode-linux package. Of course, to use this you have to create a disk image with the stuff you want installed, just as with any user-mode-linux (or qemu or vmware) emulator. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo SDK scratchbox breaks with Debian lenny upgrade
On Thursday 07 August 2008 22:55:09 Andrew Zabolotny wrote: > Graham Cobb <[EMAIL PROTECTED]> wrote: > > I am currently looking into whether I can create a UML kernel which > > runs reliably enough to do building on lenny 32-bit and 64-bit > > systems. I am optimistic but am currently having difficulty coming > > up with a UML kernel which will (i) build, and (ii) run scratchbox > > for a whole GPE build without hitting a kernel panic or breaking > > scratchbox. > > You also can try qemu-kvm which is what I currently use for > maemo development on Fedora x86_64. Since the emulated machine is > 32-bit, I have scratchbox in Ubuntu 8.04 working inside it without > problems (with vm.vdso_enabled=0 and vm.mmap_min_addr=4096 > in /etc/sysctl.conf). The overall performance drop is about 30% > compared to host OS (tested on a large build of gcc+glibc+binutils). I currently use QEMU -- it is the most reliable option but also by far the slowest. Note that my processor does not have the virtualisation extensions and so I cannot use KVM -- I get less than 10% performance on real scratchbox builds (a GPE build that takes 45 minutes native takes about 6-9 hours in my QEMU system). I use UML on another system and it is a good compromise. It achieves near native speed. My only problem is creating a reliable UML kernel. I am hopeful I will eventually succeed! But, it would be better if scratchbox and the Maemo SDK would run on debian lenny 64-bit kernels (in a chroot). Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo SDK scratchbox breaks with Debian lenny upgrade
From Thu, 7 Aug 2008 16:44:39 +0100 Graham Cobb <[EMAIL PROTECTED]> wrote: > I am currently looking into whether I can create a UML kernel which > runs reliably enough to do building on lenny 32-bit and 64-bit > systems. I am optimistic but am currently having difficulty coming > up with a UML kernel which will (i) build, and (ii) run scratchbox > for a whole GPE build without hitting a kernel panic or breaking > scratchbox. You also can try qemu-kvm which is what I currently use for maemo development on Fedora x86_64. Since the emulated machine is 32-bit, I have scratchbox in Ubuntu 8.04 working inside it without problems (with vm.vdso_enabled=0 and vm.mmap_min_addr=4096 in /etc/sysctl.conf). The overall performance drop is about 30% compared to host OS (tested on a large build of gcc+glibc+binutils). -- Andrew signature.asc Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo SDK scratchbox breaks with Debian lenny upgrade
On Wednesday 06 August 2008 13:01:14 Eero Tamminen wrote: > There was a further comment about this issue in bug: > --- > Do you have compat vdso support compiled in your kernel? > > My guess would be that the linux-image-2.6.25-2-amd64 doesn't have that > support compiled in, thus using exclusively the randomized vdso which is > unsupported by the old glibc inside scratchbox. > --- I expect this is right. My goal is to be able to use standard lenny (which will ship as Debian stable in a few weeks) kernel. I am currently looking into whether I can create a UML kernel which runs reliably enough to do building on lenny 32-bit and 64-bit systems. I am optimistic but am currently having difficulty coming up with a UML kernel which will (i) build, and (ii) run scratchbox for a whole GPE build without hitting a kernel panic or breaking scratchbox. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo SDK scratchbox breaks with Debian lenny upgrade
Hi, ext Graham Cobb wrote: > I have just installed the latest Debian lenny upgrades on one of my systems, > which installed a new linux kernel, and scratchbox has broken! This appears > to be the (well known) VDSO problem but the workround I found using Google > (echo 0 > /proc/sys/vm/vdso_enabled) does not work (that file does not > exist), neither does vdso=0 (or 2) on the boot command line. I presume the > problem is that Debian has decided to change this feature even though it > breaks user programs. > > This is a real pain. I build 40 packages every night for chinook, bora and > gregale, which, as you can guess, requires a fairly complex build > environment.Currently the builds use either chroot or user-mode-linux > environments which give reasonable speed (but builds still take up to 6 > hours!) but use the host system's kernel. I really do not want to go back to > an emulation environment, just so that I can run a separate kernel, because > that gives poor reliability and **much** slower builds -- builds will likely > take 24 hours. It also means I cannot compile modules for testing in my > normal build environment. I noticed you filed a bug about this both for maemo: https://bugs.maemo.org/show_bug.cgi?id=3479 And Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492702 Thanks! There was a further comment about this issue in bug: --- Do you have compat vdso support compiled in your kernel? My guess would be that the linux-image-2.6.25-2-amd64 doesn't have that support compiled in, thus using exclusively the randomized vdso which is unsupported by the old glibc inside scratchbox. --- > Does anyone know when scratchbox and the SDK environments will be fixed to > work with up to date Debian kernels? Note that, if the Maemo community want > programs like GPE to continue to be maintained for the 770 user community > then these fixes have to also apply to gregale (and bora for N800 users who > have never upgraded). My hopes are on the SDK+ project: http://maemo-sdk.garage.maemo.org/ It should already work fairly OK for building ARMEL packages, but currently it's tested/supports only Ubuntu Gutsy & Hardy. > In the immediate term I will go back to using the previous kernel but these > systems are my normal user and development machines so I can't live with out > of date kernels for long. I can also build my own kernel but I do want to > return to using stock Debian kernels as soon as I can. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo SDK scratchbox breaks with Debian lenny upgrade
I have just installed the latest Debian lenny upgrades on one of my systems, which installed a new linux kernel, and scratchbox has broken! This appears to be the (well known) VDSO problem but the workround I found using Google (echo 0 > /proc/sys/vm/vdso_enabled) does not work (that file does not exist), neither does vdso=0 (or 2) on the boot command line. I presume the problem is that Debian has decided to change this feature even though it breaks user programs. This is a real pain. I build 40 packages every night for chinook, bora and gregale, which, as you can guess, requires a fairly complex build environment.Currently the builds use either chroot or user-mode-linux environments which give reasonable speed (but builds still take up to 6 hours!) but use the host system's kernel. I really do not want to go back to an emulation environment, just so that I can run a separate kernel, because that gives poor reliability and **much** slower builds -- builds will likely take 24 hours. It also means I cannot compile modules for testing in my normal build environment. Does anyone know when scratchbox and the SDK environments will be fixed to work with up to date Debian kernels? Note that, if the Maemo community want programs like GPE to continue to be maintained for the 770 user community then these fixes have to also apply to gregale (and bora for N800 users who have never upgraded). In the immediate term I will go back to using the previous kernel but these systems are my normal user and development machines so I can't live with out of date kernels for long. I can also build my own kernel but I do want to return to using stock Debian kernels as soon as I can. Any suggestions are welcome. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
