[Yum-devel] arm arch handling
Dennis Gilmore
dennis at ausil.us
Tue Nov 23 04:31:39 UTC 2010
On Monday, November 01, 2010 07:41:06 am James Antill wrote:
> On Fri, 2010-10-29 at 16:36 -0500, Dennis Gilmore wrote:
> > just for added fun
> >
> > we are looking at adding support for hardware floating point in fedora
> > arm.
> >
> > which brings up how to handle this is rpm and yum
> >
> > there is three levels of ABI for floating point defined by -mfloat-abi=
> > soft
> > softfp
> > hard
> >
> > Specifying `soft' causes GCC to generate output containing library calls
> > for floating-point operations. `softfp' allows the generation of code
> > using hardware floating-point instructions, but still uses the
> > soft-float calling conventions. `hard' allows generation of
> > floating-point instructions and uses FPU-specific calling conventions.
> >
> > software compiled with soft will run on both softfp and hard. but softfp
> > and hard dont work together.
> >
> > the same hardware will run all 3. as long as it has the necessary
> > hardware.
> >
> > I need to try work out how to handle this in yum and rpm. though im still
> > trying to clarify it all.
>
> The way it works currently, in yum (and in rpm, I think) is that you
> basically have multiple lists of arches each list goes from more general
> to more specific. So Eg.
>
>
> A1 => B1 => C1
> ... => C2
>
> ...here you have four arches that yum understands, rpms for A1 run on
> all four. Those compiled for B1 run on three, and then those compiled
> for C1/C2 just run on their arch.
>
> So for arm we currently have:
>
> noarch => armv5tel => armv5tejl => armv6l => armv7l
>
> ...and we just use "os.uname()[4]" to get the basearch. So, at a guess,
> you want to create something like:
>
> ... => armv7l => armv8l => armv8sfp
> ... => armv8hwfp
>
so what we actually have is more like
noarch => armv5tel => armv5tejl => armv6l => armv7l
=> armv5telhfp => armv5tejlhfp => armv6lhfp => armv7lhfp
=> armv5telsfp => armv5tejlsfp => armv6lsfp => armv7lsfp
where the first which is what we have now runs on the other 2
Ive been reading some conflicting info on the compatabilites.
Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.baseurl.org/pipermail/yum-devel/attachments/20101122/f8cdac42/attachment.pgp>
More information about the Yum-devel
mailing list