Re: armelfp: new architecture name for an armel variant

2010-07-11 Thread Wookey
+++ Paul Brook [2010-07-11 14:16 +0100]: > > The tricky-bit here is that instruction-set extensions (VFP3, thumb2, > > NEON) and instruction set versions (v4, v5, v6a, v7) can also be > > incompatible in the sense that they won't run on hardware without > > those features. But I really think we sho

Re: Problems cross building arm debian packages

2010-07-11 Thread Loïc Minier
On Thu, May 06, 2010, Francois Goudal wrote: > So it looks good. But actually, if I look at what's inside this > package, I can see that the hello binary is actually an x86 ELF > binary file :( > > Looking closer to the package build process, I can see that the > ./configure is not run with any cr

Re: armelfp: new architecture name for an armel variant

2010-07-11 Thread Paul Brook
> The tricky-bit here is that instruction-set extensions (VFP3, thumb2, > NEON) and instruction set versions (v4, v5, v6a, v7) can also be > incompatible in the sense that they won't run on hardware without > those features. But I really think we should try to deal with that by > correctly decorati

Re: armelfp: new architecture name for an armel variant

2010-07-11 Thread Paul Brook
> > The tricky-bit here is that instruction-set extensions (VFP3, thumb2, > > NEON) and instruction set versions (v4, v5, v6a, v7) can also be > > incompatible in the sense that they won't run on hardware without > > those features. But I really think we should try to deal with that by > > correctl

Re: armelfp: new architecture name for an armel variant

2010-07-11 Thread Martin Guy
On 7/11/10, Bill Gatliff wrote: > But then doesn't that mean that everything is "armel", so we never have a > hope of having Debian officially support more than one combination? Well, "armel" should be as generic as possible. In an ideal world, it would be called "arm" and run on pretty much all