Posts by One Norse

1) Questions and Answers : Unix/Linux : platform 'x86_64-pc-linux-gnu' not found (Message 30655) Posted 5 Nov 2006 by One Norse Post: You know you are using an unofficial 64bit client when you could just as easily use the official 32bit client (that is up to you). The problem is that it is far from 'just as easy' to use the 32 bit client. Using the 64 bit one involves a couple of clicks in the package manager, using the 32 bit involves more stuff that the average end user would not be familiar with. The fix for the client side developer would be to put somewhere in the code some thing like 'platform * not found' send request for platform 686' or whatever platform you want ti to report as. This would fix it for ALL project and any other future projects that some along. I agree, the person at Berkley who is in charge of the linux client application should put this in the next version. While it shouldn't be too much of a problem to do the server side part. Most projects just install boinc and use as it with little cusomisation other than to get the project running. We 64-bit linux users just want the same level of automation: install it and it runs! I agree that Rosetta, or any other boinc project, is not necessarily the right place to do the modifications. On the other hand, if word got out that Rosetta's software was cooperating automatically with the 64-bit versions of the linux client, you might just be able to recruit a bunch of pretty high performance pc's to your project without 'too much of a problem.' :)
2) Questions and Answers : Unix/Linux : platform 'x86_64-pc-linux-gnu' not found (Message 30654) Posted 5 Nov 2006 by One Norse Post: Additional thoughts on my earlier post: In step 5, if you wanted to just start the boinc client without restarting the system, you can open a shell, and type in: /etc/init.d/boinc-client start and you should get up and running with less hassle. Even though its not as automatic as installing boinc through apt, as a work-around this approach has a couple of advantages over creating app-info files. 1) You only need to do the modification once, and it should work for every boinc project you want to join. 2) You will not need to edit the app-info files every time a project gets updated. 3) You will not need to edit the configuration files when the boinc client gets updated, just stop the boinc client: /etc/init.d/boinc-client stop download the new self-extracting archive in the same place as you downloaded the first one, extract it. then start the new boinc client: /etc/init.d/boinc-client start
3) Questions and Answers : Unix/Linux : platform 'x86_64-pc-linux-gnu' not found (Message 30646) Posted 5 Nov 2006 by One Norse Post: Gaaaah! Did you do all this just to get the 32 bit app? Well, after a lot of hunting, it amounted to not so much work.The hunting involved a little effort until I (finally) got a clue and googled "Debian boinc." and found the project pages. 1) Do the Debian installation with apt, or aptitude, or apt-whatever. I use adept with Kubuntu. (about 4 clicks of effort on my part) 2) I then uninstalled boinc using adept, but did not use the purge option. This removes the executable, but leaves the configuration files in place. apt should have a similar option. (another four clicks) 3) Get the 32 bit client: First, make a directory on the disk you want to use for boinc: mine is /mnt/hda/downloads/ Go to the Berkley boinc site:http://boinc.berkeley.edu/index.php Click on 'Download and run BOINC software Click on 'Download BOINC' and save the file to your directory. boinc comes as a 'self-extracting archive.' run it (instructions are at http://boinc.berkeley.edu/sea.php 3) Debian initializes boinc with a script file called /etc/init.d/boinc-client (this line is just a FYI) 4) The startup script reads options out of /etc/default/boinc-client (note the directory change). Edit this file (you'll need root privileges) and change the BIONC-USER, BOINC-DIR and BOINC-CLIENT so that they point to the software you just installed I prefer to comment out the original, and enter my own line so I have to original to back up to without hunting. # Original ENTRY: BOINC_USER="boinc" BOINC_USER="myusername" # Original ENTRY: BOINC_DIR="/var/lib/boinc-client" BOINC_DIR="/mnt/hda/downloads/BOINC" # Original entry: BOINC_CLIENT="/usr/bin/boinc_client" BOINC_CLIENT="/mnt/hda/downloads/BOINC/boinc_client" You have to change the BOINC-USER to someone with read/write privileges in the directory you want to use for data (using your own login should work fine). The BOINC-CLIENT must point to the executable boinc-client that was extracted from the archive. The BOINC-DATA directory could be anything to which you have read/write access. 5) Restart your system, and you should see a line about boinc being started as the system boots. If you want to be sure your changes took place, edit the /etc/init.d/boinc-client script file and change either the NAME= or DESC= lines to make a different message show up at boot. 6) To run the boinc manager, you'll need to either run it from a shell /(your directory)/boincmgr or create an icon on your desktop which points to the same executable boincmgr. All in all, it took much less effort to make the changes than it did to write this post.
4) Questions and Answers : Unix/Linux : platform 'x86_64-pc-linux-gnu' not found (Message 30621) Posted 5 Nov 2006 by One Norse Post: I ended up 'solving' the problem for now by downloading the 32 bit boinc client app from the main boinc website, and modifying the startup and configuration files that were installed by the Debian boinc installer. After adjusting a few lines to point to the newly downloaded app, it requested all 32 bit project files, and is running OK for now. I still think this issue should be dealt with by someone above the user level, especially since 64 bit machines are becoming more widely used.
5) Questions and Answers : Unix/Linux : platform 'x86_64-pc-linux-gnu' not found (Message 29604) Posted 18 Oct 2006 by One Norse Post: We don't have a 64-bit version of the client as of yet. Sorry.... -KEL How about doing a filter on the request so that instead of an error message, we AMD 64 users automatically get the 32 bit Linux app instead, at least until such time as a 64 bit app is available? Google platform 'x86_64-pc-linux-gnu' not found and you will find that there are way too many posts out there asking for info, or giving work-arounds. This should be handled either by BOINC itself, or by each application, and should be somewhat transparent to the end user. And while you're at it, take care of the freeBSD folks, too, since they have basically the same problem.