It would be best if the platform strings could uniquely identify compatible binaries. I.E. if a client has the platform arm-linux-gnu, then any arm-linux-gnu application should be able to run there.
To me it appears that is not possible for an "arm-linux-gnu" platform. There are too many incompatible ARM versions, incompatibles FPUs and incompatible ABIs. I think clients are going to have to be more specific about platforms than that. Does uname in ARM linux give enough info to identify the compatible instruction sets and ABIs? Is there another command that can do it? Is there an API that lists them? Is it found in /proc/cpuinfo? It's likely that we'll need specific code in the BOINC client to generate the ARM platform names. I'm not sure if what comes out of autoconf as a platform name is sufficient to distinguish. Anyone want to report what config.h has for the BOINC platform on various systems if you just compile without setting the BOINC platform? On Fri, Jul 5, 2013 at 4:18 AM, Lars Bausch <[email protected]> wrote: > > Am 03.07.13 21:56, schrieb Heinz-Bernd Eggenstein: > >> As you mentioned the Raspberry Pi: BOINC is available in the repo of >> Raspian, a Debian wheezy fork, and it uses the platform string >> 'arm-unknown-linux-gnueabihf'. > > In a previous definition here on the mailinglist, the string "unknown" > should not used within the plaform string. > > Lars > > > _______________________________________________ > boinc_projects mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
