Alessandro Ghedini wrote: > Hannes von Haugwitz wrote: >> A static library without krb is better than the current one which >> is not usable at all. > > That's just not true. Nothing stops you from using the static > libcurl library and linking to the shared krb5, which is installed > on pretty much every Debian system, being it priority standard.
My original purpose in building a static Darcs binary was so I could run it on a system that was too old to support a Haskell compiler -- probably Fedora Core 3 and RHEL 4. I assumed that people normally built static binaries for that reason, i.e. because they needed a program to run on a legacy host. I'm not sure such legacy hosts would have a libkrb installed that would be compatible with what a statically-linked-curl/dynamically-linked-krb binary would expect. The other part of the problem would be how to tell Darcs' build system to statically link some C libraries, but not others. Of course, that is not your problem, but it would still need to be dealt with. PS: since this ticket was opened, I have murdered the FC3/RHEL4 hosts in question -- all my hosts have OSs from 2008 or later! So I don't have a burning need for this ticket to be resolved anymore, though I'd still to help reach a consensus. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
