[ARMedslack] Mystery Prefixes

[stanley garvey]

On Feb 1, 2013 18:04 "Stuart Winter" <m-lists at biscuit.org.uk> wrote:

> > Can anyone explain the mystery prefixes on Firefox and Seamonkey?
> > Most
> > Slackware arm packages have the usual blah-*arm*tgz, however
> > mozilla-firefox has the mysterious armv6j prefix. The slackbuild
> > shows
> > only -march armv5te?
> 
> ftp://ftp.arm.slackware.com/slackwarearm/unsupported/slackwarearm-curr
> ent/source/mozilla-firefox/mozilla-firefox.SlackBuild
> 
> The -march is set to armv6j in the build script. The script
> you're looking at was not used to build the package .tgz you're
> looking at.
> 
> > Seamonkey has the prefix armhfp- I have not checked the slackbuild,
> > but
> > that would suggest hardware floating point. Could some one explain.
> > Your confused,
> 
> Yes it's named 'hfp' for that reason which is mentioned in the build
> script (at least in -current, but maybe not for 14.0).
> 
> However, there's some confusion on my part about what actually
> required an
> HFP unit and what didn't because ISTR that during various Mozilla
> releases
> (of all of the apps), at some stages I found info that led me to
> conclude
> that the newer versions had instructions for, and only ran on systems
> with
> an FPU; and other times it was due to the NEON extensions in (I think)
> armv7 machines. That made sense until someone told me that the same
> packages I thought were armv7 only, also ran on the armv6 Raspberry
> Pi.
> 
> To conclude, I don't really know apart from anything named 'armv6j'
> really
> was built for -march=armv6j. Anything named 'hfp' definitley needs a
> machine with a HFPU, but may or may not also contain the armv7 NEON
> instructions.
> 
> Needless to say I am pleased to have dropped Mozilla. What a ball ache
> that thing was with every release.
> ----------------------------------------------------------------------
> ---------------------------------
> Okay, It was me that was confused.
> I think you can use Hardware FP in any application so long as the
> application uses its own private library's, and that is what I thought
> was happening, as SlackwareARM supports devices without a HFPU I could
> not figure it out.
> Looks like Firefox might rebuild natively on a raspberry pi after all
> (day two, I kid you not!). I have put all my builds up on my ftp site
> if any one is interested, they can be used as overlays upgradepkg
> --reinstall someapplication-*tgz
> Best regards
> Stanley,
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20130202/78913cee/attachment.html>