** Branch linked: lp:ubuntu/qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921078
Title:
FATAL: kernel too old ← how old is too old?
To manage notifications about this bug go to:
https://bugs.l
** Branch linked: lp:ubuntu/qemu-linaro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921078
Title:
FATAL: kernel too old ← how old is too old?
To manage notifications about this bug go to:
https:/
And there was much rejoicing: https://staging.launchpad.net/~nick-
moffitt/+archive/arm/+build/3206390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921078
Title:
FATAL: kernel too old ← how old is
This bug was fixed in the package qemu-linaro - 1.0.50-2012.02-0ubuntu1
---
qemu-linaro (1.0.50-2012.02-0ubuntu1) precise; urgency=low
* New upstream release.
* Pass --enable-uname-release=2.6.32 for the user emulation builds, so that
we have a sensible baseline kernel value r
Oh bah. Turns out this failed because my patch only set the uname for
the dynamically-linked qemu-user builds, not the static ones that we're
using. :/ Attached is a slightly better (i.e., working) patch.
** Patch added: "qemu-linaro-921078.patch"
https://bugs.launchpad.net/ubuntu/+source/eg
Ok, so the build log certainly shows the option being picked up but it
sure isn't helping uname. Will dig deeper here.
> The continued failure could simply be because the current ARM chroots
> aren't up-to-date with the more recently-relaxed libc6,
No, the uname output shows that the qemu change
Also, Steve's comment above that "The precise eglibc on amd64 and armel
has 2.6.24 as a minimum kernel version" is demonstrably false.
MIN_KERNEL_SUPPORTED in precise on arm* is still set to 2.6.31. In
light of that, my above chroot-refreshing dance won't help Nick at all.
Other than "newer is be
The continued failure could simply be because the current ARM chroots
aren't up-to-date with the more recently-relaxed libc6, and you need to
chroot in and run apt-get to get a shinier one. I'll update both right
now, and see if that helps you any (assuming staging is pulling chroots
from producti
Picking an actual oneiric build chroot for linux-ti-omap:
(menkalinan)root@menkalinan:/home/buildd/build-3ef7062d83f8928431f66a0007c2517aca725dca/chroot-autobuild#
chroot . uname -a
Linux menkalinan 2.6.24-30-xen #1 SMP Mon Jan 2 21:13:17 UTC 2012 armv7l armv7l
armv7l GNU/Linux
Build log for qe
Nick,
The precise eglibc on amd64 and armel has 2.6.24 as a minimum kernel
version, so this should only be happening with the armel code when it
sees a kernel < 2.6.31. Can I see the build log for the qemu package,
to try to figure out why the setting isn't sticking?
Also, if you could run the a
Hmm, it still got https://staging.launchpad.net/~nick-
moffitt/+archive/arm/+build/3206257 spitting out
https://staging.launchpadlibrarian.net/92471525/buildlog_ubuntu-precise-
armel.apturl_0.5.1ubuntu1_CHROOTWAIT.txt.gz to me. I wonder if this is
because it's happening in the chroot update code t
thanks, Steve! I'm shoving a new qemu package through our builders now,
and I'll try building precise packages again once I get the base guest
image upgraded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921078
Title:
FATAL: kernel too old ← how old is too old?
To manage notifications about this bug go to:
https://bugs.launchpad.net
Trivial patch to set 2.6.32 for the uname by default. I think this
makes sense for us to apply in the package, but I'd like Nick to test to
confirm that the eglibc 2.6.31 minimum doesn't result to more
unimplemented syscall problems.
** Patch added: "qemu-linaro-921078.patch"
https://bugs.lau
** Also affects: qemu-linaro (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921078
Title:
FATAL: kernel too old ← how old is too old?
To manage n
On second thought, since this *should* be fixed on the qemu side (either
by changing the default behavior of uname() within qemu, or by setting
an appropriate QEMU_UNAME value), and the latter seems to be
straightforward to export globally (barring questions about how exactly
to do this in the buil
The handling code in the libc6.preinst is as follows:
# The GNU libc requires a >= 2.6.18 kernel, except on m68k where a
# 2.6.32 kernel is needed.
if [ "$realarch" != m68k ]
then
# Ubuntu buildd limitation: allow just 2.6.15, although 2.6.18 is
require
There are two issues here:
1) For precise armel, we need glibc to support 2.6.24-30-xen as the
minimum kernel revision in order for arm PPAs to work. If this presents
serious performance issues, please describe them. Running that forward
to the precise kernel should be an option in the Q timefra
18 matches
Mail list logo
