Hi Jon,
On Jan 29, 2014, at 4:23 PM, Jon Sonntag wrote:
> I'm guessing that in order to make OS X work the same way that the
> BOINC client reports the device vendor instead of the platform name and
> platform vendor since both of those would be "Apple" and make it difficult
> to keep the CUDA vs
That's good news. I'm planning on making all the next Collatz CPU
applications OpenCL based, so AMD, NVIDIA and Intel covers Windows and
Linux. I'm guessing that in order to make OS X work the same way that the
BOINC client reports the device vendor instead of the platform name and
platform vendo
Jon:
The current BOINC client checks for all OpenCL/CPU drivers
(currently Intel, AMD, and NVIDIA;
any combination of these may exist on a given machine).
It reports these to the server in an array called
host.host_info.opencl_cpu_prop[]; the number of entries is
host.host_info.num_opencl_cpu_pl
Hello,
>Gesendet: Mittwoch, 29. Januar 2014 um 19:41 Uhr
>Von: "Jon Sonntag"
>
>My only hesitation with backports is the warning on the home page which
>states: "Backports cannot be tested as extensively as Debian stable, and
>backports are provided on an as-is basis, with risk of incompatibiliti
My only hesitation with backports is the warning on the home page which
states: "Backports cannot be tested as extensively as Debian stable, and
backports are provided on an as-is basis, with risk of incompatibilities
with other components in Debian stable. Use with care!"
So, I went ahead and ins
28. Januar 2014 um 21:08 Uhr
> Von: "Rom Walton"
> An: "Steffen Möller" , "Jon Sonntag"
>
> Cc: "BOINC Developers Mailing List @berkeley.edu"
> Betreff: RE: [boinc_dev] GLIBC 2.15 required for BOINC Manager?
>
> At this point, our bu
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of
"Steffen Möller"
Sent: Sunday, January 26, 2014 5:36 AM
To: Jon Sonntag
Cc: BOINC Developers Mailing List @berkeley.edu
Subject: Re: [boinc_dev] GLIBC 2.15 required for BOINC Manager?
Hi Jon,
&g
Hi Jon,
> Debian 7.3 (stable) uses glibc v2.13, Debian Jessie (testing) uses v2.17,
> and Debian Sid (unstable) uses v2.18 so it looks like they've changed their
> minds. However, at present, the only way to run the current BOINC client
> on the current Debian version is to use either the "testi
Debian 7.3 (stable) uses glibc v2.13, Debian Jessie (testing) uses v2.17,
and Debian Sid (unstable) uses v2.18 so it looks like they've changed their
minds. However, at present, the only way to run the current BOINC client
on the current Debian version is to use either the "testing" or "unstable"
"First of all, the glibc is no more"
Interesting, as glibc stable is at 2.17 in Gentoo, with 2.18-r1 awaiting
stable status.
On 01/25/2014 07:10 PM, Jon Sonntag wrote:
9down vote
BOINC 7.2.33 requires GLIBC v2.15. That's a problem as only v2.13 exists
even with the latest Debian install. H
9down vote
BOINC 7.2.33 requires GLIBC v2.15. That's a problem as only v2.13 exists
even with the latest Debian install. Here's what I've found as the
"solution" which means to me that BOINC should be downgraded to v2.13 IMO
as I do not believe BOINC should be using any "experimental" version an
11 matches
Mail list logo
