Would anyone know how to add a command to the `make test` procedure?
The Makefile lacks a recipe with $(CC), so I don't see how things
being compiled.
The idea is to find a suitable recipe, and add a step to code sign the
executable. (There's too many executables to do this by hand).
Jeff
--
On Wed, 9 Oct 2013, Jeffrey Walton wrote:
Would anyone know how to add a command to the `make test` procedure?
The Makefile lacks a recipe with $(CC), so I don't see how things being
compiled.
You're supposed to first build curl and libcurl in the root tree, then cd
tests and make should wo
On Wed, Oct 9, 2013 at 5:01 AM, Daniel Stenberg wrote:
> On Wed, 9 Oct 2013, Jeffrey Walton wrote:
>
>> Would anyone know how to add a command to the `make test` procedure?
>>
>> The Makefile lacks a recipe with $(CC), so I don't see how things being
>> compiled.
>
> You're supposed to first build
lib/curl_setup_once.h assumes lwIP on Windows uses 'SetLastError()'
to set network errors. It doesn't; it uses 'errno'. Hence this little
patch:
--- g:/MingW32/src/inet/curl/Git-latest/lib/curl_setup_once.h 2013-02-23
19:58:58 +
+++ g:/MingW32/src/inet/curl/lib/curl_setup_once.h 2013-
On Wed, 9 Oct 2013, Gisle Vanem wrote:
lib/curl_setup_once.h assumes lwIP on Windows uses 'SetLastError()' to set
network errors. It doesn't; it uses 'errno'. Hence this little patch:
Thanks, pushed!
--
/ daniel.haxx.se
---
Lis
I'm sure someone will find use for penalty values.
I don't think it's easy to use them right:
only get requests are pipelined, server "decides" on download and
especially chunk length, then the client is probably interested in how
long the transfer is going to take rather than bytes transferred, s
On Wed, 9 Oct 2013, Dima Tisnek wrote:
Can I just remind you that we don't top-post on this list!
I'm sure someone will find use for penalty values.
I don't think it's easy to use them right: only get requests are pipelined,
server "decides" on download and especially chunk length, then the c
In Curl_connecthost(), there's a loop to call singleipconnect() for
each address. This loop breaks when it gets a non-bad file descriptor.
But, 99% of libcurl invocations use non-blocking sockets, especially
in the current era of even the "easy" interface using the "multi"
back-end.
This effective
