Daniel Stenberg and Tor Arnsten, I just read your post where you advise us to:
>I think you should rather try
>with ONLY removing the "-qnoansialias -qhalt=e -O2" options and see if that
>can possibly make things different.
We just tried running:
$ xlc -DHAVE_CONFIG_H -I../include/curl -I../
>
> Hello, I basically did a copy-paste of the WRITEFUNCTION example found on
> this site and on other forums, but for some reason, it crashes every time.
> When I debugged, I found that the last variable going to the callback
> function (void* stream in the code below) is NULL thus causing a memor
On Mon, 21 Jan 2013, Mischa Salle wrote:
OpenSSL is really pain if 'someone' is trying to clean-up stuff in
mid-program. Is curl_easy_reset() doing any OpenSSL cleanup? It shouldn't,
right?
Nope.
All tries were with exactly the same URL. The same website is listening both
on 80 and 443. The
On Sat, Jan 19, 2013 at 2:57 PM, Daniel Stenberg wrote:
> Indeed. I'm adding that too now. Will push in a short while.
>
Looks like the web pages for curl_easy_send and curl_easy_recv mention the
disconnection cases now. Thank you for updating the docs.
--
On Tue, 22 Jan 2013, Frank Chang wrote:
However, when we manually enter the following command line directive. we
obtain the result shown below.
Right, when you compile something very different you don't get the problem.
You already knew that since you've compiled a lot of other source files f
Tor Arnsten, We followed the following steps on IBM-AIX:
export CC=xlc
./configure
make
and progress.c is unable to build correctly with the Makefile and libtool.
However, when we manually enter the following command line directive. we
obtain the result shown below. If you have the time, co
"LRN" wrote:
compiled object files that go into libcurl. So the header tells
it to link to dllimport mprintf functions, while the object files
provide only normal mprintf functions for internal use.
Right, unless you put a -DCURL_STATICLIB in your CFLAGS.
And link with a static libcurl.a Thus
On Tue, Jan 22, 2013 at 1:12 AM, Frank Chang wrote:
> Tor Arnsten, We just tried ./configure CC=xlc followed by make. The IBM-AIX
> compiler error log is shown below.
> It may be either an IBM-AIX xlc internal compiler error or a problem in
> the progress.c source file. If you have time, could
