67ff8e3ea3
many third-party libs and tools have problems. When curl is built without --disable-shared, the testing is done with a front-end script which makes the valgrind testing include (ba)sh as well and that often causes valgrind errors. Either we improve the valgrind error scanner a lot to better identify (lib)curl errors only, or we disable valgrind checking by default
_ _ ____ _ ___| | | | _ \| | / __| | | | |_) | | | (__| |_| | _ <| |___ \___|\___/|_| \_\_____| README.win32 Read the README file first. Curl has been compiled, built and run on all sorts of Windows and win32 systems. While not being the main develop target, a fair share of curl users are win32-based. The unix-style man pages are tricky to read on windows, so therefore are all those pages converted to HTML as well as pdf, and included in the release archives. The main curl.1 man page is also "built-in" in the command line tool. Use a command line similar to this in order to extract a separate text file: curl -M >manual.txt