![]() |
|
Home | Help | Status | Forums | Glossary | Account
|
log in |
Message boards : Pirate Applications : Yello 6.04
Author | Message |
---|---|
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. ;-) | |
ID: 8378 | Rating: 0 | rate:
![]() ![]() ![]() | |
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 | |
ID: 8380 | Rating: 0 | rate:
![]() ![]() ![]() | |
| |
ID: 8381 | Rating: 1 | rate:
![]() ![]() ![]() | |
Contact wrote: Since hello 6.05 didn't run on Win98, I was expecting the same for yello 6.04. 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 | |
ID: 8382 | Rating: 0 | rate:
![]() ![]() ![]() | |
Well, it works well enough on my ppc64. It does help to have the source and compile it myself. | |
ID: 8405 | Rating: 0 | rate:
![]() ![]() ![]() | |
trigggl wrote: Well, it works well enough on my ppc64. It does help to have the source and compile it myself. 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 | |
ID: 8406 | Rating: 0 | rate:
![]() ![]() ![]() | |
My Linux host is also trying to download cube executables, but is stalled somewhere in the middle of the road for a long time. | |
ID: 8410 | Rating: 0 | rate:
![]() ![]() ![]() | |
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 | |
ID: 8412 | Rating: 0 | rate:
![]() ![]() ![]() | |
Pepo 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? ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8413 | Rating: 0 | rate:
![]() ![]() ![]() | |
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 .-) ![]() | |
ID: 8435 | Rating: 0 | rate:
![]() ![]() ![]() | |
Wormholio wrote:
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. | |
ID: 8437 | Rating: 0 | rate:
![]() ![]() ![]() | |
Pepo 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 /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 | |
ID: 8439 | Rating: 0 | rate:
![]() ![]() ![]() | |
Wormholio wrote:
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 .-) ![]() | |
ID: 8442 | Rating: 0 | rate:
![]() ![]() ![]() | |
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 | |
ID: 8443 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Pirate Applications : Yello 6.04
Home | Help | Status | Forums | Glossary | Account
|