curl-users
Re: Gopher support
Date: Tue, 29 Jan 2008 20:06:52 -0800
On Wed, Jan 30, 2008 at 12:37:34AM +0100, Kristian Kjeldsen wrote:
> It's not my burning desire to gopher as much as it is the fact that the
> original curl that ships with my box has support for it. When building my
> optimized replacement, i'd ideally like all the features present in the slow
> version. Stock curl:
>
> curl 7.13.1 (powerpc-apple-darwin8.0) libcurl/7.13.1 OpenSSL/0.9.7l
> zlib/1.2.3
> Protocols: ftp gopher telnet dict ldap http file https ftps
> Features: IPv6 Largefile NTLM SSL libz
>
> Something tells me there were valid reasons for its removal, nevertheless,
> it is something i desire, in order for my replacement to have more features
> than the original, not less.
Well, there was a good reason it was removed--it didn't work. Or, at least
people suspected it didn't work--the lack of public gopher servers made it
difficult to verify :^)
> Earliest source i see is 7.14, i'll look it over to see if it has gopher
> support. I'm not trying to make this a problem for the community, this is
> something i'm very content to hack with in my own little world (& time).
It was removed in 7.15.2.
> On a sidenote, optimizations went great, i build the curl tool with
> -mdynamic-no-pic and just use --disable-shared, it works like a charm! I
> could maybe manually tweak the makefile, it seems libcurl uses its own setup
> of compiler flags, to disallow -mdynamic-no-pic for the shared stuff. I'm
> learning about the project on a source level now, many things left to
> discover. The only thing i'd want now is a fully static version of the
> tool+lib, so that it could all benefit from -mdynamic-no-pic.
The tool+lib are treated pretty much as a unit by the build system. I don't
think there's any way to specify flags for only one and not the other.
You could always build it twice.
>>> Dan
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has movedReceived on 2008-01-30