Re: [boinc_dev] new options, and build problems

Actually, the ./configure is not suitable for building the client on the Mac for general distribution, because we need to build for three different architectures (PowerPC, i386, x86_64) and combine them in universal binaries. For this reason, the Mac build (using XCode) also uses its own manu

Re: [boinc_dev] Some suggestions (UPS followup, Mac manager)

>When i download boinc for the mac (6.10.21) it is a folder with >several items in it other than the actual installer. "extras" as a >folder contains COPYING, COPYING.LESSER, COPYRIGHT, and the >uninstall boinc application. When you click on the item >COPYING.LESSER it won't open because the O

[boinc_dev] MAC OS X CUDA App in BOINC

On Tue Dec 29 12:11:24 PST 2009 Jon Sonntag wrote: >I've got a CUDA app working for OS X. It is built with CUDA 2.2 (32-bit). >It runs OK in standalone mode, so the next step is getting BOINC to >acknowledge that a CUDA device exists so it can be tested within BOINC >itself. Unfortunately, I don'

Re: [boinc_dev] MAC OS X CUDA App in BOINC

library along with the cuda >app so that the MAC user doesn't have to set any environment >variables or create symbolic links. -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / s...@home Macintosh & Windows Programmer Space Sciences

Re: [boinc_dev] MAC OS X CUDA App in BOINC

ld: Library not loaded: @rpath/libcudart.dylib > Referenced from: /Library/Application Support/BOINC >Data/slots/5/../../projects/boinc.thesonntags.com_collatz/collatz_2.01_i686-apple-darwin__cuda > Reason: image not found > > >On Jan 7, 2010, at 5:35 PM, Charlie Fenton wrote: >

Re: [boinc_dev] MAC OS X CUDA App in BOINC

is going to suck swamp water for >doing work ... > > >On Jan 8, 2010, at 2:47 PM, Charlie Fenton wrote: > >> This is the same problem that einst...@home is having with their >>beta CUDA application on the Mac. We will be investigating next >>week when they ret

Re: [boinc_dev] MAC OS X CUDA App in BOINC

ion has allowed the >discovery of the GPU for CUDA. I still wonder if the application is being >compiled in the 64-bit space and so it is not finding the 32-bit libraries >regardless. >>> >>> As always, willing to lend a hand if someone tells me what they want me >to t

Re: [boinc_dev] MAC OS X CUDA App in BOINC

or if the libraries are also different. The two versions of libcuda.dylib have slightly different sizes. Cheers, --Charlie >On Jan 9, 2010, at 12:59 AM, Charlie Fenton wrote: > >> This seems to imply that you expect libcudart.dylib to be installed >> on the target system in

Re: [boinc_dev] The Dark Side

rmanently, you have certainly earned that right. All I can add, both in BOINC and in life in general is the pseudo-Latin phrase: "Illegitimi non carborundum." Thank you again for all your help in the past, and I really do hope we will see you again in the future. Cheers,

Re: [boinc_dev] API suggestion to help in user retention

gt;> >>-Original Message- >>From: David Anderson [mailto:da...@ssl.berkeley.edu] Sent: >>Wednesday, February 17, 2010 1:05 PM >>To: Rom Walton >>Cc: Charlie Fenton; BOINC Developers Mailing List >>Subject: Re: API suggestion to help in user retention >> >

Re: [boinc_dev] monitoring network usage

t;http://msdn.microsoft.com/en-us/library/aa373083(VS.85).aspx >> >>This is actually the first time I have come across this set of Windows >>APIs. -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / s...@home Macintosh & Windows Programmer Space Scien

Re: [boinc_dev] How to locate boinccmd on client

On 2/20/10, Mark Pottorff wrote: > I would like to find a reliable means of locating (on all supported > platforms) the full path to the boinccmd executable from an application > running in a slots directory. At 9:29 PM -0300 2/20/10, Nicolás Alvarez wrote: >On Mac, I think boinccmd isn't inst

Re: [boinc_dev] How to locate boinccmd on client

ccmd is if the user seperates the data >directory from the BOINC client code. > >Running Microsoft's "System Idle Process" will never help cure cancer, >AIDS nor Alzheimer's. But running rose...@home just might! >http://boinc.bakerlab.org/rosetta/ > >--- O

Re: [boinc_dev] compiling boinc on OS X snow leopard

>Travis Desell > >1-518-867-1054 >Worldwide Computing Laboratory ( http://wcl.cs.rpi.edu/ ) >milky...@home ( http://milkyway.cs.rpi.edu/ ) >Rensselaer Polytechnic Institute, 110 8th Street, Troy NY 12180, USA >-------

Re: [boinc_dev] Text and screen colors.

At 8:21 AM -0400 3/15/10, john.mcl...@sybase.com wrote: >Better would be to get the background color and pick a slightly different >background color for the alternate stripes based on the background color. That sounds good in theory, but I'm not sure it is so simple in practice. For example, for

[boinc_dev] Building crypt_prog on the Mac

At 11:27 AM -0700 4/2/10, David Anderson wrote: >BuildMacBoinc.sh is for building the API and client, not for crypt_prog. >libjpeg isn't needed from crypt_prog. >-- David You should be able to build crypt_prog using configure/make. Perhaps someone from one of the other projects can tell you how

Re: [boinc_dev] building boinc on snow leopard - can't get jpeg-6b anymore

At 14:18:47 -0400 Fri, 2 Apr 2010, Desell wrote: >Also, the BuildMacBoinc.sh script doesn't work because jpeg-6b isn't found at: >ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz You can find many download sites for jpeg-6b at:

Re: [boinc_dev] Boinc on USB Stick

Hello Yoyo, Rom and I have 3 questions for you regarding your request for Boinc on a USB Stick. [1] At 13:56:56 PDT Tue May 11, 2010 Jorden van der Elst wrote: >Use a cc_config.xml file with the following entries: > > > >1 > > I don't think this is what you want; it will make it impossible to

Re: [boinc_dev] OpenCL support?

I checked the NVIDIA link and found the following information for the Mac: >OpenCL drivers are released as part of the Mac OS X Showleopard >operating system. So apparently no additional drivers are needed, though it's unclear whether the NVIDIA CUDA drivers are needed for OpenCL. There is no m

Re: [boinc_dev] Bug: BOINC 6.10.56, Problem with Apple Mac operating system information.

c OS X 10.6.3 (10D573) >>Kernel Version: Darwin 10.3.0 >>Boot Volume: Alan Stafford Int 1 >>Boot Mode: Normal >>Computer Name: Alan Stafford's Computer 1 >>User Name: Alan Stafford (Alan) >>Secure Virtual Memory: Not

Re: [boinc_dev] Bug: BOINC 6.10.56, Problem with Apple Mac operating system information.

10.3.x The third part of the Darwin version number should be ignored; as far as I have seen, it is always zero. -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / s...@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley _

Re: [boinc_dev] Bug: BOINC 6.10.56, Problem with Apple Mac operating system information.

At 10:05 AM +0100 6/4/10, Alan Stafford wrote: >My operating system is not Darwin, Darwin is my kernel. You need to >change, "Operating System" to "Kernel Version. Thank you for your comments. I think this is a question of semantics. The man page for uname (1) says: > -s print the

Re: [boinc_dev] BOINC reporting "no usable GPUs found" although they should be present

Hi Robin, You need to download and install the CUDA driver as described at The direct download link for the current Mac driver is Cheers, --Ch

Re: [boinc_dev] BOINC reporting "no usable GPUs found" although they should be present

Yes, that is normal. It is a shortcoming of the NVIDIA CUDA driver for the Mac. I'm afraid the information about downloading the CUDA driver is a bit subtle. There's a link on the BOINC download pages and t

Re: [boinc_dev] BOINC reporting "no usable GPUs found" although they should be present

At 12:34 AM +0200 7/9/10, Robin Kipp wrote: >Sorry, here's another one. I didn't notice another line in the log >file, saying: > >Fr 9 Jul 00:12:48 2010NVIDIA GPU 1 (not used): >GeForce GT 120 (driver version unknown, CUDA version 3010, compute >capability 1.1, 512MB, 90 GFLOPS

Re: [boinc_dev] BOINC reporting "no usable GPUs found" although they should be present

gt;I don't have time ATM to go looking for for the threads ... maybe >this afternoon. > > >On Jul 8, 2010, at 4:45 PM, Charlie Fenton wrote: > >> At 12:34 AM +0200 7/9/10, Robin Kipp wrote: >>> Sorry, here's another one. I didn't notice ano

Re: [boinc_dev] BOINC Manager status column might be partly inaccessible

Hi Robin, Actually, I now notice that information only appears for GPU tasks. I am running Einstein, but not Collatz; I do see this information for Einstein tasks. I just checked and confirmed that VoiceOver does say this information correctly on BOINC 6.10.56 and OS 10.6.4. Also, the Einstei

Re: [boinc_dev] Remote GUI RPC won't work with wildcard IP addresses

You're correct: BOINC doesn't know about wildcards. If there is a small enough range of IP addresses, you could just list all the possibilities in the remote_hosts.cfg file, one per line. Also, you can put either IP addresses or host names in this file. If you have a list of the possible host

Re: [boinc_dev] Why not keep it simple?

be the easiest way to switch to the advanced menu. It is a challenge to design a UI that works well for those with disabilities users in addition to being optimized for the majority of users. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / s...

Re: [boinc_dev] Why not keep it simple?

ced view help links. >>(The Boinc FAQs would serve this purpose admirably but I imagine that >>such a link is a no-no because it isn't official Boinc documentation.) >>It might also help if, just as more than one Command button is provided >>by def

Re: [boinc_dev] (no subject)

Hello Fabio and Travis, I'm somewhat puzzled by your posts. First, which version of BOINC are you trying to build? In other words, which version did you check out from SVN? The setupForBOINC.sh scripts accepts neither -dev nor -no64bit as valid arguments; the only valid argument is -clean. T

Re: [boinc_dev] MacBuild error ...

Hello Fabio and Travis, (Posting again with correct subject line.) I'm somewhat puzzled by your posts. First, which version of BOINC are you trying to build? In other words, which version did you check out from SVN? The setupForBOINC.sh scripts accepts neither -dev nor -no64bit as valid argu

Re: [boinc_dev] MacBuild error ...

Hello Fabio and Travis, I have updated the build scripts and the build instructions in the SVN trunk. You can find the new instructions in the source tree's boinc/mac_build directory and on the web at Cheers, --Charlie ___

[boinc_dev] Updated Mac build instructions for project applications

I've updated the instructions for building project applications on Macintosh at . These revised instructions explain how to build applications using XCode 3.2 under OS 10.6.x that will run on: PowerPC Macs back to OS 10.3.9 32-bit Intel ba

Re: [boinc_dev] Environment variables : suggestions

Hello Arnaud, The code that sets up these environment variables is found in two places. The first place is in ACTIVE_TASK::start() which in the 6.12.15 tag is at lines 822 through 855 in client/app_start.cpp. The second location of this code applies only to the Mac. It is in lines 85 through

Re: [boinc_dev] Environment variables : suggestions

Hello Arnaud, Please ignore my comments about the name of your project directory. I see now that it is indeed the URL of your project. Cheers, --Charlie ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinf

Re: [boinc_dev] OpenCL device selection

Hi Oliver, As Rom writes, we are still working on sorting out the OpenCL detection and implementation. One major issue will be when a client has multiple GPUs and a mix of CUDA and OpenCL tasks or a mix of CAL and OpenCL tasks (or even all three.) From what we have seen so far, each framewor

Re: [boinc_dev] OpenCL device selection

Hi Oliver, At 01:01:17 PDT 2011 4/12/11, Oliver Bock wrote: >Ok, so when the core client enumerates the devices, it requests >CL_DEVICE_TYPE_GPU devices only, right? Yes. At 10:17 AM +0200 4/12/11, Oliver Bock wrote: >On 4/11/11 23:00 , Charlie Fenton wrote: >> As Rom write

[boinc_dev] Why the New Simple View?

If you have been testing the 6.13.0 alpha release, you have probably seen the reworked Simple View. I am writing to explain the reasons for the changes and to explain the rationale for its design. The old Simple View (as in 6.12.33) has a number of basic problems. It uses mostly non-standard

[boinc_dev] Skin Changes for New Simple View

In a separate email, I outlined the reasons for redesigning the Simple View and the rationale for its design. While there might still be some adjustments, we don't anticipate further major changes. To better understand the information below, please try running the 6.13.x alpha release, availab

Re: [boinc_dev] Settings/Options in the BOINC manager

I had already decided to separate out the exclusive apps into a separate dialog. I originally implemented it as an additional pane to the computing preferences because that was easier to do, but I have concluded that was a mistake, especially since the Clear button does not apply to it. Cheers

Re: [boinc_dev] Settings/Options in the BOINC manager

On Aug 24, 2011, at 10:32 AM, Jorden van der Elst wrote: > I like the idea of integrating the options dialog window into the > preferences window. Perhaps that the Clear button can be moved to the > separate tabs that use it? > That way you could integrate everything into one window. Before I ad

Re: [boinc_dev] Settings/Options in the BOINC manager

ore easily done per tab rather than for the entire > dialog. > > jm7 > > > > Charlie Fenton > keley.edu> To &g

Re: [boinc_dev] lib/parse.h fails to compile in latest trunk

That should be fixed now. Cheers, --Charlie On Aug 25, 2011, at 12:59 AM, yoyo wrote: > Hello, > > I updated to the latest trunk version. I got now a compile error in > lib/parse.h, that strtoull is already defined in stdlib.h. Before make I > did ./_autosetup and ./configure --disable-client -

Re: [boinc_dev] lib/parse.h fails to compile in latest trunk

This should also be fixed now. Cheers, --Charlie On Aug 25, 2011, at 1:13 AM, Christian Benjamin Ries wrote: > And I got with same procedure: > > coproc.cpp: In member function ‘int COPROC_NVIDIA::parse(XML_PARSER&)’: > coproc.cpp:468: error: ‘parse_opencl’ was not declared in this scope > copr

Re: [boinc_dev] Building boincmgr (trunk) fails

This has been true for quite some time. The obvious work-around is to cd to the clientgui directory and run make there. If anyone understands configure and make well enough to fix this, it would be appreciated. The one person ay SSL who has this knowledge hasn't had time to look into it. Che

Re: [boinc_dev] IPV6?

versions of c-ares have fixed this problem, so version 6.13 can support IPV6 on Macs. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley On Sep 13, 2011, at 6:11 AM, john

Re: [boinc_dev] Wrapper deletes checkpoint file

acs. Please let me know if this is a problem. We continue to support PowerPC Macs in BOINC 6.12.x, but have discontinued PowerPC Mac support as of BOINC 6.13.x. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows

Re: [boinc_dev] [boinc_alpha] libnotify4 and BOINC

breaks. But in the future, if you provide patches for the Mac, please check that they work with the recommended build procedures. Thanks again for your interest in BOINC. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Wind

Re: [boinc_dev] BM and NVDA

Hello Krzysztof, We have rewritten the Simple View for BOINC 7.0.x to use only standard controls so that it should work with all screen readers. Would you be kind enough to check whether the new Simple View works with NVDA? Thank you. Cheers, --Charlie -- Charlie Fenton

Re: [boinc_dev] [boinc_projects] [boinc_alpha] NVidia Kepler GTX 680 released

On Mar 28, 2012, at 12:22 PM, David Anderson wrote: > NvAPI looks promising. > The official doc is here: > http://developer.nvidia.com/nvapi > > However - inexplicably - it seems to exist only for Windows. > Anyway, I'll investigate using NvAPI after 7.0 is out. Remember also that on the Mac, Ope

[boinc_dev] BOINC 7.0.31 Public Release (Mac Only)

Because Apple is expected to release OS 10.8 Mountain Lion within a few days, we have promoted BOINC 7.0.31 to be a public release for the Macintosh only. The main differences from 7.0.28 are changes to the Mac installer to work properly under OS 10.8. There is no pressing need for users to up

[boinc_dev] Changes to text rendering in graphics apps

It was recently brought to our attention that the licensing is unclear for some of the code we have been using to display text strings in our graphics (screensaver) applications. We have made some changes to ensure that our code is properly licensed under the Free Software Foundation's GNU Less

Re: [boinc_dev] Changes to text rendering in graphics apps

cided to remove ttfont.cpp > from the graphics library to avoid this problem > -- D > > On 07-Aug-2012 8:12 AM, Oliver Bock wrote: >> On 8/3/12 12:07 , Charlie Fenton wrote: >>> If your project's graphics applications use the BOINC graphics >>> library's s

Re: [boinc_dev] openCL (not used) issue

I wonder if you had the latest Intel drivers. Please see the forum thread at: which seems to imply there is a newer Intel driver available on Intel's web page:

Re: [boinc_dev] Slideshow screen saver

I believe that World Community rid's "Say no to Schistosoma 6.20" application has a slide-show screensaver. Cheers, --Charlie On Sep 14, 2012, at 7:20 AM, Coss, David wrote: > Well, considering I'm going to do it anyways, I'd be glad to work on it > there. Unless someone else wants to... > >

Re: [boinc_dev] ttfonts and uc2_graphics

Hi David, Please see If you want your graphics application to display text, you must add the files api/ttfont.cpp and api/ttfont.h to your application yourself. They are not included in the basic library build because they requir

Re: [boinc_dev] [PATCH] problem in get_vendor in api/boinc_opencl.cpp

_INVALID_DEVICE_TYPE. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley On Jan 10, 2013, at 10:51 AM, Heinz-Bernd Eggenstein wrote: > Hi all! > > Someone

Re: [boinc_dev] Errors building wrapper for Android

s written in C++. You may also wish to disable > this option if you are compiling older C++ programs that don't use exception > handling. So it seems that, if it is needed at all, it should be specified for CFLAGS and is unnecessary for CXXFLAGS. Cheers, --Charlie -- Charlie Fenton

[boinc_dev] Rename MainActivity class?

he different projects, such as BOINC_UI and BOINC_EXAMPLE. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley ___ boinc_dev mailin

[boinc_dev] Syntax Errors in BOINC UI

Hi Joachim, et al, As I wrote before, I am new to both Java and Android, so please forgive my ignorance. When I add the BOINC UI project to Eclipse (selecting "Android Project from Existing Code"), it complains of 27 errors ("Java Problems") in file ProjectsActivity.java. I am using the lates

Re: [boinc_dev] Syntax Errors in BOINC UI

On Jan 28, 2013, at 7:10 AM, Joachim Fritzsch wrote: > Seems like the support library is missing in the project. > > I am using a few classes that got introduced with API level 11 and later. > Many people are still using the versions before, so I added an official > backwards support library fro

Re: [boinc_dev] Rename MainActivity class?

Hi Joachim, > But if it causes trouble with Eclipse, let's rename them... Please do so. Thanks. Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley On Jan 28

Re: [boinc_dev] Feature request for server config

course, CAL does not support Macs, but Apple's OpenCL implementation supports most modern ATI/AMD GPUs and is standard on current versions of OS X. So it also makes sense to have OpenCL but not CAL applications for Macs. Cheers, --Charlie -- Charlie Fenton

Re: [boinc_dev] [PATCH] OpenBSD support

As Rom wrote, I fixed the Mac issue by manually adding HAVE_XLOCALE_H to mac_build/config.h, because neither the Mac builds nor the Windows builds use configure / make. I noticed that Rom later removed the references to HAVE_XLOCALE_H, which puzzled me. This is the first I have heard of anyt

Re: [boinc_dev] Android battery issues

On Feb 8, 2013, at 12:18 AM, David Anderson wrote: > Maybe a better policy is: > start computing only when the battery is 95% charged. > stop computing if the charge goes down > resume computing then the charge returns to its max level I think that people want their phones to charge to 100% as qui

Re: [boinc_dev] Android battery issues

the charge has returned to its "max level"? Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley ___ boin

Re: [boinc_dev] patch for FTBFS

I checked your change in. Cheers, --Charlie On Apr 11, 2013, at 1:15 AM, Gianfranco Costamagna wrote: > diff --git a/client/app_control.cpp b/client/app_control.cpp > index c805ce4..2ae7c83 100644 > --- a/client/app_control.cpp > +++ b/client/app_control.cpp > @@ -215,8 +215,8 @@ static void kil

Re: [boinc_dev] Accelerator type identification issue

BOINC's GPU device number as displayed in the Event Log is for a physical GPU. In the case to which Raistmer refers, the first ATI GPU (GPU 0) is capable of (and recognized by) CAL but not OpenCL. The second ATI GPU (GPU 1) is recognized by and capable of both CAL and OpenCL. Thus, BOINC _cor

Re: [boinc_dev] Accelerator type identification issue

it gets it from the type argument to the function, if present. Next it tries to get the gpu_opencl_dev_index and gpu_device_num from the init_data.xml file. If that fails, it gets the gpu_device_num from the --device argument. Cheers, --Charlie On Apr 15, 2013, at 4:09 PM, Charlie Fenton wrote:

Re: [boinc_dev] Accelerator type identification issue

Hello Raistmer, I am sorry if I have not been clear enough in my responses. We have _already_ done what you are requesting, but not the way you suggest. Doing it the way you suggest would be incompatible with existing applications, servers and older versions of BOINC and so would break older

Re: [boinc_dev] Accelerator type identification issue

On Apr 16, 2013, at 1:22 AM, Raistmer the Sorcerer wrote: > >NOTE: The new boinc_get_opencl_ids() API is 100% backward compatible with > >older versions of the BOINC client. From the source file's comments: > > It's not. > When I call it under older BOINC I get no valid CL context so ap will fail

Re: [boinc_dev] Accelerator type identification issue

s minds running down the > wrong path. Right you are! Thank you for your eagle eye. It seems no matter how many times I proof read my writing, something always slips by. Cheers, --Charlie > From: Charlie Fenton > To: Raistmer the Sorcerer > Cc: boinc_dev@ssl.berkeley.edu > Sent:

Re: [boinc_dev] Accelerator type identification issue

On Apr 16, 2013, at 3:26 AM, Richard Haselgrove wrote: > Typo alert. "The ... file that the BOINC client writes to each slot" (second > paragraph) is of course init_data.xml, and I suspect the sample file contents > likewise. Calling it app_info.xml may set people's minds running down the > wron

[boinc_dev] Moving forward

I am going to leave this discussion with one last thought, because it is starting to feel more like an argument than a friendly, cooperative discussion. BOINC has been one of the early adopters of GPU computing. When we began working on it, OpenCL was still under development. Yes, if we were t

[boinc_dev] GPU Plan Classes

As of BOINC 7.0.65, the BOINC client assumed that any CAL-capable GPU was also OpenCL-capable, and so reported the to the server that way. I have since checked in code that corrects this assumption and should report correctly to the server. Because of limited information available from CAL a

Re: [boinc_dev] OpenCL on NVidia and device enumeration

assigned by the client. I recently wrote a detailed explanation to this (boinc_dev) email list. Here it is again: On Apr 15, 2013, at 4:09 PM, Charlie Fenton wrote: > BOINC's GPU device number as displayed in the Event Log is for a physical > GPU. In the case to which Raistmer refers

Re: [boinc_dev] OpenCL on NVidia and device enumeration

determine that they are both running on the same device? Cheers, --Charlie -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / SETI@home Macintosh & Windows Programmer Space Sciences Laboratory UC Berkeley ___ boinc_dev

Re: [boinc_dev] Exiting remote BOINC Manager exits local client(silently)

At 12:34 PM +0100 5/19/09, Richard Haselgrove wrote: >The BOINC v6.6 managers (currently .20 and .28) show much more >screen 'flicker' when updating data for running tasks than earlier >managers - comparing the current unified task list view with earlier >'Grid' views in v6.4.5, v6.2.49, and v5.

Re: [boinc_dev] BOINC All versions download page

Hello Maureen, We removed it because we want to phase out the V5 clients, and users would be more inclined to use a V5 client if it is shown on the download_all page, even though it is marked as an older version. We have now also removed the 5.10.45 and 5.8.16 versions for Linux for the same r

Re: [boinc_dev] BOINC All versions download page

ntelx86.exe> and <http://boinc.berkeley.edu/dl/boinc_5.10.45_windows_x86_64.exe> Cheers, --Charlie At 10:45 AM +0100 5/20/09, Richard Haselgrove wrote: >Charlie Fenton wrote > >>Hello Maureen, >> >>We removed it because we want to phase out the V5 clients, and us

Re: [boinc_dev] Voice over for Mac OS X

As of version 6.6.24, the user can press command-shift-A (Mac) or control-shift-A (Windows, Linux) to switch to the Advanced View. I added this specifically to aid vision-impaired users. Unfortunately, WCG who designed and implemented the Simple View specified there should be no menus in Simpl

Re: [boinc_dev] Splitting libboinc?

If you do rearrange the libraries, please post a clear description of exactly what should now be in each library, so I can easily adjust the Mac projects to match the other platforms. I'll also need to update the build instructions at , and other

Re: [boinc_dev] boinc's choice of Mac subversion (processor choice) to send

also run s...@home with QCN on this Macbook and >that's the i686-apple version (they don't seem to have a separate >x86_64 Apple anyway) > >Carl Christensen >carl...@yahoo.com http://www.geocities.com/carlgt1 > > > -- Charlie Fenton

Re: [boinc_dev] boinc's choice of Mac subversion (processor choice) to send

At 5:35 PM -0300 6/25/09, Nicolás Alvarez wrote: >El Jue 25 Jun 2009 17:22:23 Charlie Fenton escribió: >> OS 10.5 is a full 64-bit OS, as long as the CPU is 64-bit capable >> (Intel Core 2 Duo or later). Only the original Intel Core Duo >> (without the "2") in th

Re: [boinc_dev] Snow Leopard Compatibility (Wikidot)

ne >>>successfully upgraded from 10.5 to 10.6 without reinstalling? Does >>>that mean that WUs in progress are lost during the upgrade? If it >>>isn't accurate someone should change it. >>> >>>Sincerely, >>>Jack >>> >> >>

[boinc_dev] Another change for Mac OS 10.6 Snow Leopard

boincscr) also use AppKit, but they do not run setuid or setgid, so the new restrictions do not apply to them either. No other component of BOINC uses the AppKit framework. -- Charlie Fentoncharl...@ssl.berkeley.edu BOINC / s...@home Macintosh &

Re: [boinc_dev] Using BOINC on the Mac from a console?

Download the UNIX Command-line version of BOINC for the Mac from: It includes the boinccmd command-line tool. Instructions can be found at . Since you've already installed BOINC, just c

Re: [boinc_dev] could the git comment be more descriptive or better empty ?

Hi Toralf, By "what has changed" do you mean the list of modified files or a brief description / explanation of what has changed? For those of us who use a GUI interface to GIT like SourceTree, it is _very_ helpful for the GIT commit message to start with a brief description of _what_ has chan

Re: [boinc_dev] prepared to accept patches for llvm, i.e. clang, compatibility?

Hi Steffen, For what it's worth, I have been building BOINC on the Mac using the "LLVM GCC 4.2" compiler for quite some time with no problems. (This is one of two compilers provided as part of Xcode 4.4.1, the other is "Apple LLVM Compiler 4.0".) According to Apple's documentation: > In Xcode

Re: [boinc_dev] OS X apps

Hi Jon, This message is normal and expected. If you look at the switcher.cpp code, you will see that it sets the DYLD path again to take care of the previous environment being ignored. Cheers, --Charlie On Aug 4, 2013, at 1:59 PM, Bernd Machenschalk wrote: > This is not a real error message,

Re: [boinc_dev] SSE3 detection (Radim Van?o)

From my early 2008 Mac Pro running OS 10.7.5 Lion: > Thu Aug 8 02:02:47 2013 | | Starting BOINC client version 7.2.5 for > x86_64-apple-darwin > Thu Aug 8 02:02:47 2013 | | Processor: 4 GenuineIntel Intel(R) Xeon(R) CPU > E5462 @ 2.80GHz [x86 Family 6 Model 23 Stepping 6] > Thu Aug 8 02:02:4

Re: [boinc_dev] SSE3 detection (Radim Van?o)

have at least SSE3? If so, we may not > have to worry about it because SSE3 can be assumed. > > > On Thu, Aug 8, 2013 at 3:45 PM, Charlie Fenton > wrote: > From my early 2008 Mac Pro running OS 10.7.5 Lion: > > Thu Aug 8 02:02:47 2013 | | Starting BOINC client version 7

Re: [boinc_dev] SSE3 detection (Radim Van?o)

<http://en.wikipedia.org/wiki/SSE3> seems to imply that all the Intel Core series processors have SSE3. Cheers, --Charlie On Aug 8, 2013, at 3:58 PM, Charlie Fenton wrote: > I have a fairly early iMac with the Core 2 Duo processor, and it also reports > both SSE3 and SSSE3.

Re: [boinc_dev] Error 11 in OS X OpenCL apps

Hi Jon, Here is what I do to build BOINC itself. I don't know if this will help. However, the Mac stack trace code does compile properly when I use this technique. Unfortunately, I don't know what might cause the error 11 in your OpenCL apps. If you are not getting an adequate back trace fr

Re: [boinc_dev] Possible OS X Mavericks problem.

The fix is to do what the error message told him to do. When you install a new version of Mac OS X over an older version, it doesn't always preserve the boinc_master and boinc_project users and groups; in which case you need to reinstall BOINC after installing the OS. The message he quotes cle

Re: [boinc_dev] Possible OS X Mavericks problem.

fied developers (which I believe is the default setting) he should have no trouble installing current versions of BOINC and should not see that message. If he does see that message with a current version, he may have a corrupted download. Cheers, --Charlie -- Charlie Fentonc

Re: [boinc_dev] [boinc_alpha] Wxwidgets 3.0 has been finally released

Hi Gianfranco, We still need to merge the changes in master since 18 October into the wxWidgets30 branch (or perhaps the other way around) and update boinc_depends_win_vs2010 with the final wxWidgets 3.0.0 from 3.0.0-rc1 (for Windows builds). But in my preliminary tests, both the Mac and Windo

Re: [boinc_dev] [boinc_alpha] CPU throttling

The code to get CPU temperature on Apple Macintosh Intel computers has been in client/hostinfo_unix.cpp for some time. It is called int get_max_cpu_temperature(). // Check up to 10 die temperatures (TC0D, TC1D, etc.) and // 10 heatsink temperatures (TCAH, TCBH, etc.) // Returns the highest cu

Re: [boinc_dev] Problem compiling with Mac OS X 10.9 and Xcode 5.0.2 (5A3005)

Hello Francesco, Please make sure that you are building from the files in the BOINC GIT repository _master_ branch. These are the only ones which can be built as written using Xcode 5. All other branches and tags can be built only with older versions of Xcode (although it would undoubtedly be

  1   2   3   >