problem with Socket API-recv
Date: Thu, 20 Dec 2007 11:13:52 +0530
I have problem with Socket API recv function. Before Calling this
recv function, interrupt was enabled. But this recv function resets the core
interrupt in the tcp layer level. why it happens like this? If anyone
knows, reply me.
Thanks in advance.
[mailto:curl-users-bounces_at_cool.haxx.se] On Behalf Of
Sent: Wednesday, December 19, 2007 4:30 PM
Subject: curl-users Digest, Vol 28, Issue 17
Send curl-users mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of curl-users digest..."
1. Re: Sending back-to-back HTTP PUTs on same connection?
2. Re: Problems building curl (7.16.2 - 7.17.1) with Openssl
0.9.8 (Dan Fandrich)
3. Re: Problems building curl (7.16.2 - 7.17.1) with Openssl
0.9.8 (Daniel Stenberg)
Date: Tue, 18 Dec 2007 15:03:08 -0800
From: "Chris Markle" <cmarkle_at_asperasoft.com>
Subject: Re: Sending back-to-back HTTP PUTs on same connection?
To: "the curl tool" <curl-users_at_cool.haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
> > Thanks! I think maybe I should have been a little more specific
> > (remembering that cURL is command line, lib, etc.). Is there a way for
> > me to leverage this connection reuse from the command line version?
> Yes, just supply two -T options and two URLs.
Thanks! That's what I needed. Appreciate the help...
Date: Tue, 18 Dec 2007 15:05:23 -0800
From: Dan Fandrich <dan_at_coneharvesters.com>
Subject: Re: Problems building curl (7.16.2 - 7.17.1) with Openssl
Content-Type: text/plain; charset=us-ascii
On Tue, Dec 18, 2007 at 05:34:24PM -0500, Calen Pennington wrote:
> From inspection of src/Makefile, it appears that -lcrypto and -lssl
> appear in the LIBCURL_LIBS variable, but that that variable isn't being
> used to set LIBS before the implicit rule is executed:
No, the crypto libraries are not needed by curl directly and shouldn't be
linked. That change was made to libcurl between the two versions you cite.
What should be happening is that the crypto libs should be linked into
libcurl instead. What does the libcurl.so.4 link line look like? You
should also see the crypto libs references in the output of "objdump -p
Are you sure you have a 64-bit version of the OpenSSL on your system to
allow the 64 bit to compile?
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has moved ------------------------------ Message: 3 Date: Wed, 19 Dec 2007 00:07:14 +0100 (CET) From: Daniel Stenberg <daniel_at_haxx.se> Subject: Re: Problems building curl (7.16.2 - 7.17.1) with Openssl 0.9.8 To: the curl tool <curl-users_at_cool.haxx.se> Message-ID: <Pine.LNX.4.64.0712190002210.29756_at_yvahk3.pbagnpgbe.fr> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Tue, 18 Dec 2007, Calen Pennington wrote: > On 32-bit, the configure runs fine, and includes the lines: > checking for CRYPTO_lock in -lcrypto... yes > checking for SSL_connect in -lssl... yes [...] > /usr/dev_tools/170681/bin/ld: warning: libssl.so.0.9.8, needed by > ../lib/.libs/libcurl.so, not found (try using -rpath or -rpath-link) > /usr/dev_tools/170681/bin/ld: warning: libcrypto.so.0.9.8, needed by > ../lib/.libs/libcurl.so, not found (try using -rpath or -rpath-link) > ../lib/.libs/libcurl.so: undefined reference to `RAND_load_file' As you can see, it tried to link with the crypto and ssl libs but didn't find them at link time. > If I manually run the following command (note the added "-lcrypto > -lssl"), then there are no errors: But is it then really linking with and using the very same libs it didn't find in the previous command? > From inspection of src/Makefile, it appears that -lcrypto and -lssl > appear in the LIBCURL_LIBS variable src/Makefile doesn't need to have them specified, as the libcurl is linked with them and thanks to magic that will "pull in" them. As can be seen in the link failures, the linker knows what libs it should be using it just fails to find them. > Finally, this same problem does not occur in 7.16.1. Right, as back then we (probably) still provided the -l options when we linked curl too. > On 64-bit, the command I run is the same. However, during configure, the > following lines appear: > checking for CRYPTO_lock in -lcrypto... no > checking for CRYPTO_add_lock in -lcrypto... no Load config.log into your favourite editor and investigate the particular tests for SSL that failed. -- Commercial curl and libcurl Technical Support: http://haxx.se/curl.html ------------------------------ _______________________________________________ curl-users mailing list curl-users_at_cool.haxx.se http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users End of curl-users Digest, Vol 28, Issue 17 ******************************************Received on 2007-12-20