the prebuilt client doesnt work cause its build with glibc 2.4 now and building yourself requires a libcurl update.

---

the prebuilt client doesnt work cause its build with glibc 2.4 now and building yourself requires a libcurl update.

G'day Michael

Have you tried Augustine's client . If that doesn't work then of your two choices I'd go for updating curl.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

that version is also dynamically linked with glibc 2.4 ;-)

---

I tried building the 5.10.18 client (the current alpha version) on Linux (on Fedora Core 4), but it failed to build for me. I can build the current SVN HEAD, but not 5.10.18.

Now that might be because I don't understand branches in SVN as well as I did in CVS. I know CVS use of tags for both snapshots and branches was confusing, but I got used to it. Can someone who got 5.10.18 to build tell me how they checked it out?

---

-- Eric Myers

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

I tried building the 5.10.18 client (the current alpha version) on Linux (on Fedora Core 4), but it failed to build for me. I can build the current SVN HEAD, but not 5.10.18.

Now that might be because I don't understand branches in SVN as well as I did in CVS. I know CVS use of tags for both snapshots and branches was confusing, but I got used to it. Can someone who got 5.10.18 to build tell me how they checked it out?

As I wrote in this thread, checkout is quite straight-forward. It seems to me that there's something in the code that freaks out optimizers in both GCC and ICC though ...

[edit] Actually I didn't write that. Here's how I fetch sources:

svn co http://boinc.berkeley.edu/svn/branches/boinc_core_release_5_10/

[/edit]

---

Metod ...

Actually I didn't write that. Here's how I fetch sources:

svn co http://boinc.berkeley.edu/svn/branches/boinc_core_release_5_10/

That's what I tried too, as well as the ..._5_10_18 branch. The build fails on Fedora Core 4 (gcc 4.0.2). But it only fails in the scheduler, the client is "okay". Or at least it builds.

I then tried it on a Fedora Core 5 machine where I've been running the client (not often, but it was working). It fails to start due to a version number problem with curl. Not good.

The problem is that the build should be linking against a _static_ version of libcurl, not a dynamic library (Rom, I'm lookin' at you :-).

So I'd say that Linux version 5.10.18 just fails alpha test miserably.

If anyone wants to try it, I put it in http://pirates.spy-hill.net/download/alpha/ It's package up the way it comes from the build (self-installing sh script) but I recommend installation according to http://pirates.spy-hill.net/help/unix.html.

---

-- Eric Myers

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

The problem is that the build should be linking against a _static_ version of libcurl, not a dynamic library (Rom, I'm lookin' at you :-).

The same happens with 5.11.0 - my Gentoo boxes changed versions of curl - I had to recompile the BOINC source so that it linked against the new version.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

The problem is that the build should be linking against a _static_ version of libcurl, not a dynamic library (Rom, I'm lookin' at you :-).

The same happens with 5.11.0 - my Gentoo boxes changed versions of curl - I had to recompile the BOINC source so that it linked against the new version.

If you are building from source then you need the proper version of curl. And that keeps being changed as the new versions of curl provide newer features.

Once built though, the client should not need any version of curl libraries on the host. The client should be linked against the static curl library so that the user's machine does not have to have curl installed.

---

-- Eric Myers

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

If you are building from source then you need the proper version of curl. And that keeps being changed as the new versions of curl provide newer features.

My feeling was that required version of curl changes a lot because new versions of curl are supposed to fix problems with NTLM-enabled proxy servers. In fact, I'm using older curl version on my Debian Sarge system without any problem. The only thing I have to do is to patch configure.ac to test against installed curl version that matches what I have on my system.

Obviously I don't care about NTLM-enabled proxy servers 'cause I don't use any.

---

Metod ...

In fact, I'm using older curl version on my Debian Sarge system without any problem. The only thing I have to do is to patch configure.ac to test against installed curl version that matches what I have on my system.

Obviously I don't care about NTLM-enabled proxy servers 'cause I don't use any.

That would probably help Michael (the OP), providing he doesn't need to worry about NTLM proxies. He could self-compile and link to his existing curl.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1