Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

updates

  • Loading branch information...
commit 05b84bfe9161af675eed7812050e03e58b0c3479 1 parent dbfa1e5
Daniel Stenberg authored
2  docs/FEATURES
@@ -56,7 +56,7 @@ FTP
56 56
  - download
57 57
  - authentication
58 58
  - kerberos security
59  
- - PORT or PASV
  59
+ - active/passive using PORT, EPRT, PASV or EPSV
60 60
  - single file size information (compare to HTTP HEAD)
61 61
  - 'type=' URL support
62 62
  - dir listing
20  docs/INSTALL
@@ -36,8 +36,7 @@ UNIX
36 36
    The configure script always tries to find a working SSL library unless
37 37
    explicitly told not to. If you have OpenSSL installed in the default search
38 38
    path for your compiler/linker, you don't need to do anything special. If
39  
-   you have OpenSSL installed in e.g /usr/local/ssl, you can run configure
40  
-   like:
  39
+   you have OpenSSL installed in /usr/local/ssl, you can run configure like:
41 40
 
42 41
 	./configure --with-ssl
43 42
 
@@ -46,13 +45,13 @@ UNIX
46 45
 
47 46
 	./configure --with-ssl=/opt/OpenSSL
48 47
 
49  
-   If you insist on forcing a build *without* SSL support, even though you may
50  
-   have it installed in your system, you can run configure like this:
  48
+   If you insist on forcing a build without SSL support, even though you may
  49
+   have OpenSSL installed in your system, you can run configure like this:
51 50
 
52 51
         ./configure --without-ssl
53 52
 
54 53
    If you have OpenSSL installed, but with the libraries in one place and the
55  
-   header files somewhere else, you'll have to set the LDFLAGS and CPPFLAGS
  54
+   header files somewhere else, you have to set the LDFLAGS and CPPFLAGS
56 55
    environment variables prior to running configure.  Something like this
57 56
    should work:
58 57
 
@@ -72,7 +71,7 @@ UNIX
72 71
      LIBS=-lRSAglue -lrsaref
73 72
      (as suggested by Doug Kaufman)
74 73
 
75  
-   KNOWN PROBLEMS
  74
+   KNOWN PROBLEMS (these ones should not happen anymore)
76 75
 
77 76
      If you happen to have autoconf installed, but a version older than 2.12
78 77
      you will get into trouble. Then you can still build curl by issuing these
@@ -101,8 +100,8 @@ UNIX
101 100
 
102 101
    MORE OPTIONS
103 102
 
104  
-     Remember, to force configure to use the standard cc compiler if both
105  
-     cc and gcc are present, run configure like
  103
+     To force configure to use the standard cc compiler if both cc and gcc are
  104
+     present, run configure like
106 105
 
107 106
        CC=cc ./configure
108 107
          or
@@ -130,11 +129,6 @@ UNIX
130 129
 
131 130
        ./configure --with-krb4=/usr/athena
132 131
 
133  
-     If your system support shared libraries, but you want to built a static
134  
-     version only, you can disable building the shared version by using:
135  
-
136  
-       ./configure --disable-shared
137  
-
138 132
      If you're a curl developer and use gcc, you might want to enable more
139 133
      debug options with the --enable-debug option.
140 134
 
17  docs/README.win32
@@ -12,18 +12,11 @@ README.win32
12 12
   systems. While not being the main develop target, a fair share of curl users
13 13
   are win32-based.
14 14
 
15  
-  Some documentation in this archive will be tricky to read for Windows
16  
-  people, as they come in unix-style man pages. You can either download a
17  
-  freely available nroff binary for win32 (*pointers appriciated*), convert
18  
-  the files into plain-text on your neighbor's unix machine or run over to the
19  
-  curl web site and view them as plain HTML.
  15
+  The unix-style man pages are tricky to read on windows, so therefore are all
  16
+  those pages also converted to HTML and those are also included in the
  17
+  release archives.
20 18
 
21  
-  The main curl.1 man page is "built-in". Use a command line similar to this
22  
-  in order to extract a separate text file:
  19
+  The main curl.1 man page is also "built-in" in the command line tool. Use a
  20
+  command line similar to this in order to extract a separate text file:
23 21
 
24 22
         curl -M >manual.txt
25  
-
26  
-  Download all the libcurl man pages in HTML format using the link on the
27  
-  bottom of this page:
28  
-
29  
-        http://curl.haxx.se/libcurl/c/

0 notes on commit 05b84bf

Please sign in to comment.
Something went wrong with that request. Please try again.