Please post any problems with the 64 bit linux app here.

---

Im getting
Sat 22 Nov 2008 02:18:13 PM CET|Milkyway@home|Message from server: MilkyWay@home Optimized is not available for your type of computer.
on my 64 bit Ubuntu box, anything I can do about it?

Im getting
Sat 22 Nov 2008 02:18:13 PM CET|Milkyway@home|Message from server: MilkyWay@home Optimized is not available for your type of computer.
on my 64 bit Ubuntu box, anything I can do about it?

The linux binaries haven't been uploaded to the server yet -- they should be there this afternoon (i'm waiting on dave to sign them and upload them). Unfortunately all my machines are osx and the code signing process isn't available for that yet, so i need to wait for dave to do the signing :(

---

Okay, no problem. If I may ask: "Afternoon" would be afternoon CET or anything else? I'm on CET here. Or could you just give us a quick notice here when the apps are there?

Okay, no problem. If I may ask: "Afternoon" would be afternoon CET or anything else? I'm on CET here. Or could you just give us a quick notice here when the apps are there?

It's really up to whenever Dave has time to sign the binaries and put them on the server. Hopefully he's not too busy today :)

---

It would help if some libraries were linked statically, especially libgcc but also libstdc++, as not all systems will necessarily have the same GCC version as the one used to build the application.

I laid the instructions about how to do that here, here and here.

Similar recommendation also applies to the x86 application.

HTH

---

Please post any problems with the 64 bit linux app here.

I still don't get the right stuff, so I'm restricted to babysit while asking for work and delete those old energy wasting rubbish as soon as it arrives in my puter.
Is there a way to keep the outdated and wasteful 1.22 stuff away automatically?
I'd like to try the new stuff, but not under such circumstances.

---

Grüße vom Sänger

Apparently my box downloaded the new app okay (it says 1.23) but it doesn't seem to work any better than the previous version. I get a sig 11 for every single workunit.

My box is a Core2Quad 9400, not overclocked in any way, running 64 Bit Ubuntu with the latest kernel (2.6.27-4-generic). Anything else you need to know, just ask. I'm willing to do beta testing (I'm a CS student, so don't worry to confuse me or so) but for the time being I switched to "no new tasks" since a quad core trashes WUs at a rather amazing speed.

No idea so far what's wrong. I'm talking about this box:
http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=36527

With Milksop's app it worked fine. My other BOINC projects (Einstein, MalariaControl, Enigma) also work okay.

Apparently my box downloaded the new app okay (it says 1.23) but it doesn't seem to work any better than the previous version. I get a sig 11 for every single workunit.

My box is a Core2Quad 9400, not overclocked in any way, running 64 Bit Ubuntu with the latest kernel (2.6.27-4-generic). Anything else you need to know, just ask. I'm willing to do beta testing (I'm a CS student, so don't worry to confuse me or so) but for the time being I switched to "no new tasks" since a quad core trashes WUs at a rather amazing speed.

No idea so far what's wrong. I'm talking about this box:
http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=36527

With Milksop's app it worked fine. My other BOINC projects (Einstein, MalariaControl, Enigma) also work okay.

1.23 is the old application, to try out our new test app you need to enable it in your project preferences: http://milkyway.cs.rpi.edu/milkyway/prefs.php?subset=project

---

Run test applications?
This helps us develop applications, but may cause jobs to fail on your computer yes

Has been like that since yesterday...

Run test applications?
This helps us develop applications, but may cause jobs to fail on your computer yes

Has been like that since yesterday...

You might not have gotten the most recent application simply because i haven't been making massive batches of workunits yet, and they're being snatched up quicker than you could get one.

---

Sounds likely. But that would be a real problem, since the old "standard" app doesn't run on my system. Any idea how I can avoid downloading "old" workunits and crashing them, apart from waiting out until the new app is the only one in use?

... Any idea how I can avoid downloading "old" workunits and crashing them, apart from waiting out until the new app is the only one in use?

You could create an app_info.xml file to make sure you're only using the milkyway 0.2 application.
The app_info.xml can be created with a simple text editor and should look like this:

<app_info>
<app>
    <name>milkyway</name>
  </app>
<file_info>
  <name>milkyway_0.2_x86_64-pc-linux-gnu</name>
  <executable/>
</file_info>
<app_version>
  <app_name>milkyway</app_name>
  <version_num>2</version_num>
  <file_ref>
    <file_name>milkyway_0.2_x86_64-pc-linux-gnu</file_name>
    <main_program/>
  </file_ref>
</app_version>
</app_info>

EDIT: This file has to be put into Milkyway's project folder, most likely to be found under var/lib/boinc-client. ;-)

---

Lovely greetings, Cori

Great idea, thanks. Don't worry, I know where the file goes, I've done quite a bit of beta testing over at Einstein. The idea to solve the problem like this simply didn't occur to me ;-)

Great idea, thanks. Don't worry, I know where the file goes, I've done quite a bit of beta testing over at Einstein.

Cool!

The idea to solve the problem like this simply didn't occur to me ;-)

Hehe, in Germany we have a saying which would translate like "You don't see the wood because of so many trees". *grin*

---

Lovely greetings, Cori

You could create an app_info.xml file to make sure you're only using the milkyway 0.2 application.
The app_info.xml can be created with a simple text editor and should look like this:
EDIT: This file has to be put into Milkyway's project folder, most likely to be found under var/lib/boinc-client. ;-)

And I think BOINC has to be shut down and restarted to recognise this, at least mine DLed some old stuff without it.

---

Grüße vom Sänger

Yup. When fiddling around with any *.xml file BOINC should always be shut down before. ;-)

---

Lovely greetings, Cori

This seems to have helped - kinda. The good news is my BOINC client has stopped downloading old stuff. The bad news is that it seems to be unable to download the new app, showing up in the logs like this:
Mon 24 Nov 2008 12:10:31 AM CET|Milkyway@home|Backing off 43 min 41 sec on download of milkyway_0.2_x86_64-pc-linux-gnu

It should work if you download the app from here and place it in the milkyway directory.

---

Finally i got one optimized WU with the app_info.xml tip.
As soon as it started i got a compute error.
I'm using boinc 6.2.12 on Ubuntu 8.10 amd64.

Here's the output:

Mon 24 Nov 2008 11:20:20 AM CET|Milkyway@home|Starting task nm_test11_394_1227466867_1 using milkyway version 2
Mon 24 Nov 2008 11:20:21 AM CET|Milkyway@home|Computation for task nm_test11_394_1227466867_1 finished
Mon 24 Nov 2008 11:20:21 AM CET|Milkyway@home|Output file nm_test11_394_1227466867_1_0 for task nm_test11_394_1227466867_1 absent