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

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

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

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.

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?

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?

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 .-)

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.

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?

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.

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 [...]

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.

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 .)