Re: dpkg-cross, dpkg-architecture and arch names

2007-02-27 Thread Lennart Sorensen
On Tue, Feb 27, 2007 at 12:44:31PM +0100, Volker Grabsch wrote: > While "linux-i386" in Debian currently means "i486", > a "w32-i386" should stand for "i586". Why? Win NT 3.x ran fine on a 386 (with enough ram), and many windows 32bit systems ran on 486's. Perhaps Win 2k or XP requires a pentium

Re: dpkg-cross, dpkg-architecture and arch names

2007-02-27 Thread Volker Grabsch
Dear Developers, it's interesting to see the dicussion reappear which I started last year. In that time dpkg-architecture was too inflexible and I fear that's still the case. Anyway, I'll try to summarize the problems I encountered. In the last year I performed an intensive research for some week

Re: dpkg-cross, dpkg-architecture and arch names

2007-02-26 Thread Guillem Jover
[ Please use my debian address as I prefer to use that hat for dpkg stuff. ] Hi, On Tue, 2007-02-27 at 00:03:30 +, Wookey wrote: > I noticed that dpkg-cross didn't automatically recognise armel when > provided with an updated dpkg-architecture. > > This is because it has its own table of d

dpkg-cross, dpkg-architecture and arch names

2007-02-26 Thread Wookey
I noticed that dpkg-cross didn't automatically recognise armel when provided with an updated dpkg-architecture. This is because it has its own table of debian->gnu arch names: 'i386' => 'i486-linux-gnu', 'sparc' => 'sparc-linux-gnu',