[maemo-developers] [maemo-developers] Package architecture armel vs gnueabi-linux-arm
From: Neal H. Walfield neal at walfield.orgDate: Tue Feb 27 13:48:49 EET 2007
- Previous message: [maemo-developers] Package architecture armel vs gnueabi-linux-arm
- Next message: Programmatically Enabling Hardware Keys
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At Sat, 24 Feb 2007 12:59:34 +0100, "Neal H. Walfield" <neal at walfield.org> wrote: > > At Mon, 11 Sep 2006 13:00:32 +0300, > Marius Vollmer <marius.vollmer at nokia.com> wrote: > > > > "ext Niels Breet" <maemo at breet.com> writes: > > > > > After doing some upgrades to Sardine, dpkg fails on a lot of packages > > > because of: > > > package architecture (armel) does not match system (gnueabi-linux-arm) > > > > > > Does this mean that you have introduced a new architecture and as a result of > > > that all current packages are incompatible? (Again) > > > > Nonono, sorry. Dpkg in Sardine was somehow miscompiled for Sardine, > > but I haven't had time to fix it. Will do it immediately... > > I have installed the following rootstrap: > > http://repository.maemo.org/stable/gregale/armel/Maemo_Dev_Platform_v2.2_armel-rootstrap.tgz > > and am experiencing this same problem. Did this somehow creep back > in? Is there an easy fix? The problem is that the debian-sarge devkit provides dpkg et al., which take precedence over the ones provided by the rootstrap. The solution was to install just the debian devkit not both the debain and debian-sarge devkits.
- Previous message: [maemo-developers] Package architecture armel vs gnueabi-linux-arm
- Next message: Programmatically Enabling Hardware Keys
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]