Pirates@Home logo

Pirates@Home

Berkeley Open Infrastructure
BOINC!
for Network Computing
Home Help Status Forums Glossary Account

Yello 6.04

log in

Advanced search

Message boards : Pirate Applications : Yello 6.04

Author Message
Profile Ageless
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 20 Jul 04
Netherlands
Machinae Supremacy
Credit: 1,524.1
RAC: 0.00
Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Walk Plank
Message 8378 - Posted: 8 Feb 2009 | 22:41:48 UTC

Anyone seen any problems with Yello 6.04? Other than that it's very difficult to get them. It took me 32 minutes just to get one, at 175 bytes/sec. ;-)
____________
Jord.

Used to be a single voice that vanished in a crowd. Vague just like a distant sun when hidden by the clouds.
Found a way to surface and to speak my truth aloud. Be powerful. Stand fast and proud

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8380 - Posted: 9 Feb 2009 | 13:33:45 UTC - in response to Message 8378.

Ageless wrote:
It took me 32 minutes just to get one, at 175 bytes/sec. ;-)

There was quite a feeding frenzy when the new app was released, which slowed down the connection, both inbound and outbound. That seems to have passed.

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Contact
Volunteer tester
Avatar
Send message
Joined: 29 Aug 04
Canada
BOINC Synergy
Credit: 37,127.0
RAC: 0.00
Joined: Aug 29, 2004
Verified: Nov 10, 2011
Dubloons: 3
Pieces of Eight: 3
Punishment: Misfit
Message 8381 - Posted: 9 Feb 2009 | 14:53:38 UTC - in response to Message 8378.


Yello 6.04 runs without error on Win98!

Since hello 6.05 didn't run on Win98, I was expecting the same for yello 6.04.
Checking the release notes I'm guessing yello works on Win98 because it was built with MSVC++ 2003 on Windows 2000 while hello was built with MSVC++ 2008 on Windows XP.
____________
have fun

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8382 - Posted: 9 Feb 2009 | 15:07:51 UTC - in response to Message 8381.

Contact wrote:
Since hello 6.05 didn't run on Win98, I was expecting the same for yello 6.04.
Checking the release notes I'm guessing yello works on Win98 because it was built with MSVC++ 2003 on Windows 2000 while hello was built with MSVC++ 2008 on Windows XP.

That is the big difference, so I'm also guessing that is the explanation.

There may be a way to get MSVC++ 2008 to also support Win98, but since I'm still new to using it I probably don't have the right configuration setting for that.

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile 7ri9991 [MM]
Volunteer tester
Avatar
Send message
Joined: 3 Feb 09
United States
SETI.USA
Credit: 2,934.2
RAC: 0.00
Joined: Feb 3, 2009
Verified: Jan 16, 2010
Dubloons: 3
Pieces of Eight: 10
Punishment: Canon Fodder
Message 8405 - Posted: 13 Feb 2009 | 12:09:36 UTC

Well, it works well enough on my ppc64. It does help to have the source and compile it myself.

I do have a question, though. If I upgrade to a newer version of boinc, do I need to recompile yello or whatever to run on it? Recently, Gentoo updated portage to a new version of boinc without keeping the ebuild for the old one. I updated to the new one, but then I had to recompile my setiathome_enhanced, or so I thought. The bad thing is you need the boinc source to compile just about anything to run on it. So whenever I install from portage, I then download the source and build it without installing it.

I'm just wondering if there's an easier way or is this just the situation required by people running anonymous?

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8406 - Posted: 13 Feb 2009 | 13:42:28 UTC - in response to Message 8405.

trigggl wrote:
Well, it works well enough on my ppc64. It does help to have the source and compile it myself.

I do have a question, though. If I upgrade to a newer version of boinc, do I need to recompile yello or whatever to run on it?

Short answer: you shouldn't. The binaries are compiled to run most newer flavors of Linux without need of special libraries or versions.

The thing that seems to trip this up on Linux is glibc. Older Linux boxes have a version that seems to be incompatible with apps built against newer versions. One way around this is to build the apps on a really old Linux box.

Since this is a test project, we'll be interested in anything you can report about what you try and what works and what doesn't, if you are willing.
____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Pepo
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 13 Sep 04
Slovakia
TeamVision42
Credit: 928.1
RAC: 0.00
Joined: Sep 13, 2004
Verified: Aug 4, 2009
Dubloons: 3
Pieces of Eight: 5
Punishment: Cat o' Nine Tails
Message 8410 - Posted: 13 Feb 2009 | 17:05:19 UTC

My Linux host is also trying to download cube executables, but is stalled somewhere in the middle of the road for a long time.

Additionaly all cube 6.02 and yello 6.04 apps failed there - yes it is a pretty old host.
____________
Peter .-)

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8412 - Posted: 13 Feb 2009 | 17:33:52 UTC - in response to Message 8410.
Last modified: 13 Feb 2009 | 17:34:14 UTC

Pepo wrote:
My Linux host is also trying to download cube executables, but is stalled somewhere in the middle of the road for a long time.

My network connection gets really bad whenever I release a new app version, so I've throttled back a bit so I can get some work done. But I will let the new cube out of the box when I don't need the connection, and it settles down after everyone has downloaded the new app.


____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8413 - Posted: 13 Feb 2009 | 17:35:53 UTC - in response to Message 8410.

Pepo wrote:

Additionaly all cube 6.02 and yello 6.04 apps failed there - yes it is a pretty old host.

The kernel does not look that old on it. It's usually the 2.4 kernels that have problems. Though it's not actually the kernel that is the problem, it's glibc or libstdc or libstdc++ . What distribution/version do you have?

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Pepo
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 13 Sep 04
Slovakia
TeamVision42
Credit: 928.1
RAC: 0.00
Joined: Sep 13, 2004
Verified: Aug 4, 2009
Dubloons: 3
Pieces of Eight: 5
Punishment: Cat o' Nine Tails
Message 8435 - Posted: 15 Feb 2009 | 22:30:05 UTC - in response to Message 8413.

Wormholio wrote:
The kernel does not look that old on it. It's usually the 2.4 kernels that have problems. Though it's not actually the kernel that is the problem, it's glibc or libstdc or libstdc++ . What distribution/version do you have?

It is Red Hat Enterprise Linux 4, 2 1/2 years. From ldd:
libstdc++.so.6 (GLIBCXX_3.4.4) => not found
libstdc++.so.6 (GLIBCXX_3.4.6) => not found
libstdc++.so.6 (GLIBCXX_3.4) => /usr/lib/libstdc++.so.6
[...]
____________
Peter .-)

Profile 7ri9991 [MM]
Volunteer tester
Avatar
Send message
Joined: 3 Feb 09
United States
SETI.USA
Credit: 2,934.2
RAC: 0.00
Joined: Feb 3, 2009
Verified: Jan 16, 2010
Dubloons: 3
Pieces of Eight: 10
Punishment: Canon Fodder
Message 8437 - Posted: 16 Feb 2009 | 15:02:46 UTC - in response to Message 8406.

Wormholio wrote:
trigggl wrote:
If I upgrade to a newer version of boinc, do I need to recompile yello or whatever to run on it?

Short answer: you shouldn't. The binaries are compiled to run most newer flavors of Linux without need of special libraries or versions.

The thing that seems to trip this up on Linux is glibc. Older Linux boxes have a version that seems to be incompatible with apps built against newer versions. One way around this is to build the apps on a really old Linux box.

Since this is a test project, we'll be interested in anything you can report about what you try and what works and what doesn't, if you are willing.

I meant I upgraded boinc. I'm actually using a very recent kernel (2.6.28) with the latest stable glibc.

I basically don't do much beyond setting my C*FLAGS to -O3, mtune=power3, -pipe, etc... and adjust the Makefiles to point to my boinc build and prefix locations. Also, I change the host type from i686 to powerpc64. I think I can compile just about anything if I have all of the dependencies. Should I be keeping my builds as generic as possible for the projects sake? Perhaps I could send a few generic builds out for testing on other ppc64 hosts. Surely a build on an IBM power running linux will work on a Mac running linux. It just might not work the other way around due to the inclusion of altivec on the Mac.

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8439 - Posted: 16 Feb 2009 | 18:03:43 UTC - in response to Message 8435.
Last modified: 16 Feb 2009 | 18:04:37 UTC

Pepo wrote:

It is Red Hat Enterprise Linux 4, 2 1/2 years. From ldd:
libstdc++.so.6 (GLIBCXX_3.4.4) => not found
libstdc++.so.6 (GLIBCXX_3.4.6) => not found
libstdc++.so.6 (GLIBCXX_3.4) => /usr/lib/libstdc++.so.6

Hmmm, that is not good. RHEL 4 is one I'd hope would work. Just for the record, the app was built on Fedora Core 4, which is older (I think) that RHEL 4. And ldd -v shows the app wants

/usr/lib/libstdc++.so.6:
ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
libgcc_s.so.1 (GCC_4.2.0) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GLIBC_2.0) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GCC_3.3) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GCC_3.0) => /lib/libgcc_s.so.1
libc.so.6 (GLIBC_2.4) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
libc.so.6 (GLIBC_2.2) => /lib/libc.so.6

So in this case the problem is that glibc on your machine is too new, not too old. I find that odd.

Check /usr/lib for links the library you do have with more specific version names.

A test we might run here would be to include MY version of the .so with the app bundle, and see if your machine links against that instead of the one on your system.

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Pepo
Chief Petty Officer
Volunteer tester
Avatar
Send message
Joined: 13 Sep 04
Slovakia
TeamVision42
Credit: 928.1
RAC: 0.00
Joined: Sep 13, 2004
Verified: Aug 4, 2009
Dubloons: 3
Pieces of Eight: 5
Punishment: Cat o' Nine Tails
Message 8442 - Posted: 17 Feb 2009 | 15:22:59 UTC - in response to Message 8439.

Wormholio wrote:

Hmmm, that is not good. RHEL 4 is one I'd hope would work. Just for the record, the app was built on Fedora Core 4, which is older (I think) that RHEL 4. And ldd -v shows the app wants [...]

So in this case the problem is that glibc on your machine is too new, not too old. I find that odd.

Check /usr/lib for links the library you do have with more specific version names.


OK, I've previously stripped the list to show just the missing versions. The full requirements list list is
ldd -v yello_6.04_i686-pc-linux-gnu
./yello_6.04_i686-pc-linux-gnu: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.4' not found (required by ./yello_6.04_i686-pc-linux-gnu)
./yello_6.04_i686-pc-linux-gnu: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.6' not found (required by ./yello_6.04_i686-pc-linux-gnu)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0070b000)
libm.so.6 => /lib/tls/libm.so.6 (0x003c1000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0069e000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x004ef000)
libc.so.6 => /lib/tls/libc.so.6 (0x00294000)
/lib/ld-linux.so.2 (0x00276000)

Version information:
./yello_6.04_i686-pc-linux-gnu:
libgcc_s.so.1 (GCC_3.0) => /lib/libgcc_s.so.1
libm.so.6 (GLIBC_2.0) => /lib/tls/libm.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.2) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/tls/libc.so.6
libpthread.so.0 (GLIBC_2.2) => /lib/tls/libpthread.so.0
libpthread.so.0 (GLIBC_2.0) => /lib/tls/libpthread.so.0
libpthread.so.0 (GLIBC_2.1) => /lib/tls/libpthread.so.0
libstdc++.so.6 (GLIBCXX_3.4.4) => not found
libstdc++.so.6 (GLIBCXX_3.4.6) => not found
libstdc++.so.6 (GLIBCXX_3.4) => /usr/lib/libstdc++.so.6
libstdc++.so.6 (CXXABI_1.3) => /usr/lib/libstdc++.so.6
/usr/lib/libstdc++.so.6:
libc.so.6 (GLIBC_2.1.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.2) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/tls/libc.so.6
libgcc_s.so.1 (GCC_3.3) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GCC_4.2.0) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GCC_3.0) => /lib/libgcc_s.so.1
libgcc_s.so.1 (GLIBC_2.0) => /lib/libgcc_s.so.1
/lib/tls/libm.so.6:
ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
libc.so.6 (GLIBC_2.1.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/tls/libc.so.6
/lib/libgcc_s.so.1:
libc.so.6 (GLIBC_2.2.4) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/tls/libc.so.6
/lib/tls/libpthread.so.0:
ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2
ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
libc.so.6 (GLIBC_2.1.3) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.3.2) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.2) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/tls/libc.so.6
libc.so.6 (GLIBC_PRIVATE) => /lib/tls/libc.so.6
/lib/tls/libc.so.6:
ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2
ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
ld-linux.so.2 (GLIBC_2.0) => /lib/ld-linux.so.2


A test we might run here would be to include MY version of the .so with the app bundle, and see if your machine links against that instead of the one on your system.
This might be interesting to try .)
____________
Peter .-)

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 8443 - Posted: 17 Feb 2009 | 15:54:00 UTC - in response to Message 8442.

Pepo wrote:
A test we might run here would be to include MY version of the .so with the app bundle, and see if your machine links against that instead of the one on your system.
This might be interesting to try .)

Another thing to explore is how much of this can be linked statically rather than using dynamic libraries? I know the graphics libraries need to be dynamic, to match what is installed on the hardware. But stdlibc++ and glibc? I wonder...

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Post to thread

Message boards : Pirate Applications : Yello 6.04

Home Help Status Forums Glossary Account


Return to Pirates@Home main page


Copyright © 2017 Capt. Jack Sparrow