curl: remove inapporpriate file from curl release

This is the adaptation for the a bugfix upstream
The inappropriate file src/tool_hugehelp.c presence in the curl 7.36 release
interfered with the upstream fix for
https://sourceforge.net/p/curl/bugs/1350/

Signed-off-by: Tudor Florea <tudor.florea@enea.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>

2 files changed, 8204 insertions, 0 deletions

diff --git a/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch b/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch
new file mode 100644
index 0000000000..e4b8fe2ab6
--- /dev/null
+++ b/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch
@@ -0,0 +1,8203 @@
+Upstream-Status: Backport [to be fixed in 7.37.0]
+Signed-off-by: Tudor Florea <tudor.florea@enea.com>
+
+diff -ruN a/src/tool_hugehelp.c b/src/tool_hugehelp.c
+--- a/src/tool_hugehelp.c	2014-03-25 11:29:49.000000000 +0100
++++ b/src/tool_hugehelp.c	1970-01-01 01:00:00.000000000 +0100
+@@ -1,8196 +0,0 @@
+-#include "tool_setup.h"
+-#ifndef HAVE_LIBZ
+-/*
+- * NEVER EVER edit this manually, fix the mkhelp.pl script instead!
+- * Generation time: Tue Mar 25 11:29:49 2014
+- */
+-#ifdef USE_MANUAL
+-#include "tool_hugehelp.h"
+-void hugehelp(void)
+-{
+-   fputs(
+-"                                  _   _ ____  _\n"
+-"  Project                     ___| | | |  _ \\| |\n"
+-"                             / __| | | | |_) | |\n"
+-"                            | (__| |_| |  _ <| |___\n"
+-"                             \\___|\\___/|_| \\_\\_____|\n"
+-"\n"
+-"NAME\n"
+-"       curl - transfer a URL\n"
+-"\n"
+-"SYNOPSIS\n"
+-"       curl [options] [URL...]\n"
+-"\n"
+-"DESCRIPTION\n"
+-"       curl  is  a tool to transfer data from or to a server, using one of the\n"
+-"       supported protocols (DICT, FILE, FTP, FTPS, GOPHER, HTTP, HTTPS,  IMAP,\n"
+-, stdout);
+- fputs(
+-"       IMAPS,  LDAP,  LDAPS,  POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS,\n"
+-"       TELNET and TFTP).  The command is designed to work without user  inter-\n"
+-"       action.\n"
+-"\n"
+-"       curl offers a busload of useful tricks like proxy support, user authen-\n"
+-"       tication, FTP upload, HTTP post, SSL connections, cookies, file  trans-\n"
+-"       fer  resume,  Metalink,  and more. As you will see below, the number of\n"
+-"       features will make your head spin!\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       curl is powered by  libcurl  for  all  transfer-related  features.  See\n"
+-"       libcurl(3) for details.\n"
+-"\n"
+-"URL\n"
+-"       The  URL  syntax is protocol-dependent. You'll find a detailed descrip-\n"
+-"       tion in RFC 3986.\n"
+-"\n"
+-"       You can specify multiple URLs or parts of URLs  by  writing  part  sets\n"
+-"       within braces as in:\n"
+-"\n"
+-"        http://site.{one,two,three}.com\n"
+-"\n"
+-"       or you can get sequences of alphanumeric series by using [] as in:\n"
+-"\n"
+-"        ftp://ftp.numericals.com/file[1-100].txt\n"
+-, stdout);
+- fputs(
+-"        ftp://ftp.numericals.com/file[001-100].txt    (with leading zeros)\n"
+-"        ftp://ftp.letters.com/file[a-z].txt\n"
+-"\n"
+-"       Nested  sequences  are not supported, but you can use several ones next\n"
+-"       to each other:\n"
+-"\n"
+-"        http://any.org/archive[1996-1999]/vol[1-4]/part{a,b,c}.html\n"
+-"\n"
+-"       You can specify any amount of URLs on the command line.  They  will  be\n"
+-"       fetched in a sequential manner in the specified order.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       You  can  specify a step counter for the ranges to get every Nth number\n"
+-"       or letter:\n"
+-"\n"
+-"        http://www.numericals.com/file[1-100:10].txt\n"
+-"        http://www.letters.com/file[a-z:2].txt\n"
+-"\n"
+-"       If you specify URL without protocol:// prefix,  curl  will  attempt  to\n"
+-"       guess  what  protocol  you might want. It will then default to HTTP but\n"
+-"       try other protocols based on often-used host name prefixes.  For  exam-\n"
+-, stdout);
+- fputs(
+-"       ple,  for  host names starting with \"ftp.\" curl will assume you want to\n"
+-"       speak FTP.\n"
+-"\n"
+-"       curl will do its best to use what you pass to it as a URL.  It  is  not\n"
+-"       trying  to  validate it as a syntactically correct URL by any means but\n"
+-"       is instead very liberal with what it accepts.\n"
+-"\n"
+-"       curl will attempt to re-use connections for multiple file transfers, so\n"
+-"       that  getting many files from the same server will not do multiple con-\n"
+-, stdout);
+- fputs(
+-"       nects / handshakes. This improves speed. Of course this is only done on\n"
+-"       files  specified  on  a  single command line and cannot be used between\n"
+-"       separate curl invokes.\n"
+-"\n"
+-"PROGRESS METER\n"
+-"       curl normally displays a progress meter during  operations,  indicating\n"
+-"       the  amount  of  transferred  data,  transfer speeds and estimated time\n"
+-"       left, etc.\n"
+-"\n"
+-"       curl displays this data to the terminal by default, so  if  you  invoke\n"
+-, stdout);
+- fputs(
+-"       curl  to do an operation and it is about to write data to the terminal,\n"
+-"       it disables the progress meter as otherwise it would mess up the output\n"
+-"       mixing progress meter and response data.\n"
+-"\n"
+-"       If you want a progress meter for HTTP POST or PUT requests, you need to\n"
+-"       redirect the response output to a file, using shell  redirect  (>),  -o\n"
+-"       [file] or similar.\n"
+-"\n"
+-"       It  is not the same case for FTP upload as that operation does not spit\n"
+-, stdout);
+- fputs(
+-"       out any response data to the terminal.\n"
+-"\n"
+-"       If you prefer a progress \"bar\" instead of the regular meter, -# is your\n"
+-"       friend.\n"
+-"OPTIONS\n"
+-"       Options  start  with  one or two dashes. Many of the options require an\n"
+-"       addition value next to it.\n"
+-"\n"
+-"       The short \"single-dash\" form of the options, -d  for  example,  may  be\n"
+-"       used with or without a space between it and its value, although a space\n"
+-"       is a recommended separator. The long  \"double-dash\"  form,  --data  for\n"
+-, stdout);
+- fputs(
+-"       example, requires a space between it and its value.\n"
+-"\n"
+-"       Short version options that don't need any additional values can be used\n"
+-"       immediately next to each other, like for example you  can  specify  all\n"
+-"       the options -O, -L and -v at once as -OLv.\n"
+-"\n"
+-"       In general, all boolean options are enabled with --option and yet again\n"
+-"       disabled with --no-option. That is, you use the exact same option  name\n"
+-, stdout);
+- fputs(
+-"       but prefix it with \"no-\". However, in this list we mostly only list and\n"
+-"       show the --option version of them. (This concept with --no options  was\n"
+-"       added  in  7.19.0.  Previously  most  options  were  toggled  on/off on\n"
+-"       repeated use of the same command line option.)\n"
+-"\n"
+-"       -#, --progress-bar\n"
+-"              Make curl display progress as a simple progress bar  instead  of\n"
+-"              the standard, more informational, meter.\n"
+-"\n"
+-"       -:, --next\n"
+-, stdout);
+- fputs(
+-"              Tells curl to use a separate operation for the following URL and\n"
+-"              associated  options.  This  allows  you  to  send  several   URL\n"
+-"              requests,  each  with  their  own specific options, for example,\n"
+-"              such as different user names or custom requests for each. (Added\n"
+-"              in 7.36.0)\n"
+-"\n"
+-"       -0, --http1.0\n"
+-"              (HTTP)  Tells  curl to use HTTP version 1.0 instead of using its\n"
+-"              internally preferred: HTTP 1.1.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       --http1.1\n"
+-"              (HTTP) Tells curl to use HTTP version 1.1. This is the  internal\n"
+-"              default version. (Added in 7.33.0)\n"
+-"\n"
+-"       --http2\n"
+-"              (HTTP)  Tells  curl  to  issue  its  requests using HTTP 2. This\n"
+-"              requires that the underlying libcurl was built  to  support  it.\n"
+-"              (Added in 7.33.0)\n"
+-"\n"
+-"       --no-npn\n"
+-"              Disable  the  NPN  TLS  extension.  NPN is enabled by default if\n"
+-, stdout);
+- fputs(
+-"              libcurl was built with an SSL library that supports NPN. NPN  is\n"
+-"              used  by a libcurl that supports HTTP 2 to negotiate HTTP 2 sup-\n"
+-"              port with the server during https sessions.\n"
+-"\n"
+-"              (Added in 7.36.0)\n"
+-"\n"
+-"       --no-alpn\n"
+-"              Disable the ALPN TLS extension. ALPN is enabled  by  default  if\n"
+-"              libcurl  was  built with an SSL library that supports ALPN. ALPN\n"
+-, stdout);
+- fputs(
+-"              is used by a libcurl that supports HTTP 2 to  negotiate  HTTP  2\n"
+-"              support with the server during https sessions.\n"
+-"\n"
+-"              (Added in 7.36.0)\n"
+-"\n"
+-"       -1, --tlsv1\n"
+-"              (SSL) Forces curl to use TLS version 1.x when negotiating with a\n"
+-"              remote TLS server.  You can use  options  --tlsv1.0,  --tlsv1.1,\n"
+-"              and  --tlsv1.2 to control the TLS version more precisely (if the\n"
+-"              SSL backend in use supports such a level of control).\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       -2, --sslv2\n"
+-"              (SSL) Forces curl to use SSL version 2 when negotiating  with  a\n"
+-"              remote SSL server.\n"
+-"\n"
+-"       -3, --sslv3\n"
+-"              (SSL)  Forces  curl to use SSL version 3 when negotiating with a\n"
+-"              remote SSL server.\n"
+-"\n"
+-"       -4, --ipv4\n"
+-"              If curl is capable of resolving an address to multiple  IP  ver-\n"
+-"              sions  (which  it  is  if it is IPv6-capable), this option tells\n"
+-"              curl to resolve names to IPv4 addresses only.\n"
+-, stdout);
+- fputs(
+-"\n"
+-"       -6, --ipv6\n"
+-"              If curl is capable of resolving an address to multiple  IP  ver-\n"
+-"              sions  (which  it  is  if it is IPv6-capable), this option tells\n"
+-"              curl to resolve names to IPv6 addresses only.\n"
+-"\n"
+-"       -a, --append\n"
+-"              (FTP/SFTP) When used in an upload, this will tell curl to append\n"
+-"              to  the  target  file  instead  of  overwriting  it. If the file\n"
+-"              doesn't exist, it will be  created.   Note  that  this  flag  is\n"
+-, stdout);
+- fputs(
+-"              ignored by some SSH servers (including OpenSSH).\n"
+-"\n"
+-"       -A, --user-agent <agent string>\n"
+-"              (HTTP) Specify the User-Agent string to send to the HTTP server.\n"
+-"              Some  badly  done  CGIs  fail  if  this  field  isn't   set   to\n"
+-"              \"Mozilla/4.0\".  To  encode  blanks  in  the string, surround the\n"
+-"              string with single quote marks. This can also be  set  with  the\n"
+-"              -H, --header option of course.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --anyauth\n"
+-"              (HTTP) Tells curl to figure out authentication method by itself,\n"
+-"              and use the most secure one the remote site claims  to  support.\n"
+-"              This is done by first doing a request and checking the response-\n"
+-"              headers, thus possibly inducing  an  extra  network  round-trip.\n"
+-"              This  is  used  instead  of  setting  a  specific authentication\n"
+-, stdout);
+- fputs(
+-"              method, which you can do with  --basic,  --digest,  --ntlm,  and\n"
+-"              --negotiate.\n"
+-"\n"
+-"              Note  that  using --anyauth is not recommended if you do uploads\n"
+-"              from stdin, since it may require data to be sent twice and  then\n"
+-"              the client must be able to rewind. If the need should arise when\n"
+-"              uploading from stdin, the upload operation will fail.\n"
+-"\n"
+-"       -b, --cookie <name=data>\n"
+-, stdout);
+- fputs(
+-"              (HTTP) Pass the data to the HTTP server as a cookie. It is  sup-\n"
+-"              posedly  the data previously received from the server in a \"Set-\n"
+-"              Cookie:\" line.  The data should be in the format  \"NAME1=VALUE1;\n"
+-"              NAME2=VALUE2\".\n"
+-"\n"
+-"              If  no  '=' symbol is used in the line, it is treated as a file-\n"
+-"              name to use to read previously stored cookie lines  from,  which\n"
+-, stdout);
+- fputs(
+-"              should  be used in this session if they match. Using this method\n"
+-"              also activates the \"cookie parser\" which will make  curl  record\n"
+-"              incoming cookies too, which may be handy if you're using this in\n"
+-"              combination with the -L, --location option. The file  format  of\n"
+-"              the  file  to  read cookies from should be plain HTTP headers or\n"
+-"              the Netscape/Mozilla cookie file format.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              NOTE that the file specified with -b, --cookie is only  used  as\n"
+-"              input.  No cookies will be stored in the file. To store cookies,\n"
+-"              use the -c, --cookie-jar option or you could even save the  HTTP\n"
+-"              headers to a file using -D, --dump-header!\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       -B, --use-ascii\n"
+-"              (FTP/LDAP)  Enable  ASCII  transfer.  For  FTP, this can also be\n"
+-, stdout);
+- fputs(
+-"              enforced by using an URL that ends with \";type=A\".  This  option\n"
+-"              causes data sent to stdout to be in text mode for win32 systems.\n"
+-"\n"
+-"       --basic\n"
+-"              (HTTP)  Tells curl to use HTTP Basic authentication. This is the\n"
+-"              default and this option is usually pointless, unless you use  it\n"
+-"              to  override  a  previously  set  option  that  sets a different\n"
+-"              authentication method (such as --ntlm,  --digest,  or  --negoti-\n"
+-, stdout);
+- fputs(
+-"              ate).\n"
+-"\n"
+-"       -c, --cookie-jar <file name>\n"
+-"              (HTTP)  Specify to which file you want curl to write all cookies\n"
+-"              after a completed operation. Curl writes all cookies  previously\n"
+-"              read  from a specified file as well as all cookies received from\n"
+-"              remote server(s). If no cookies are known, no file will be writ-\n"
+-"              ten.  The  file  will  be written using the Netscape cookie file\n"
+-, stdout);
+- fputs(
+-"              format. If you set the file name to  a  single  dash,  \"-\",  the\n"
+-"              cookies will be written to stdout.\n"
+-"\n"
+-"              This  command  line  option will activate the cookie engine that\n"
+-"              makes curl record and use cookies. Another way to activate it is\n"
+-"              to use the -b, --cookie option.\n"
+-"\n"
+-"              If the cookie jar can't be created or written to, the whole curl\n"
+-"              operation won't fail or even report an error clearly.  Using  -v\n"
+-, stdout);
+- fputs(
+-"              will get a warning displayed, but that is the only visible feed-\n"
+-"              back you get about this possibly lethal situation.\n"
+-"\n"
+-"              If this option is used several times, the  last  specified  file\n"
+-"              name will be used.\n"
+-"\n"
+-"       -C, --continue-at <offset>\n"
+-"              Continue/Resume  a  previous  file transfer at the given offset.\n"
+-"              The given offset is the exact  number  of  bytes  that  will  be\n"
+-, stdout);
+- fputs(
+-"              skipped,  counting  from the beginning of the source file before\n"
+-"              it is transferred to the destination.  If used with uploads, the\n"
+-"              FTP server command SIZE will not be used by curl.\n"
+-"\n"
+-"              Use  \"-C  -\" to tell curl to automatically find out where/how to\n"
+-"              resume the transfer. It then uses the given  output/input  files\n"
+-"              to figure that out.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       --ciphers <list of ciphers>\n"
+-"              (SSL) Specifies which ciphers to use in the connection. The list\n"
+-"              of ciphers must specify valid ciphers. Read  up  on  SSL  cipher\n"
+-"              list           details           on           this          URL:\n"
+-"              http://www.openssl.org/docs/apps/ciphers.html\n"
+-"\n"
+-"              NSS ciphers are done differently than OpenSSL  and  GnuTLS.  The\n"
+-"              full  list of NSS ciphers is in the NSSCipherSuite entry at this\n"
+-, stdout);
+- fputs(
+-"              URL:                                          http://git.fedora-\n"
+-"              hosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html#Directives\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --compressed\n"
+-"              (HTTP) Request a compressed response using one of the algorithms\n"
+-"              curl supports, and save  the  uncompressed  document.   If  this\n"
+-"              option  is  used  and  the server sends an unsupported encoding,\n"
+-, stdout);
+- fputs(
+-"              curl will report an error.\n"
+-"\n"
+-"       --connect-timeout <seconds>\n"
+-"              Maximum time in seconds that you allow  the  connection  to  the\n"
+-"              server  to  take.   This  only limits the connection phase, once\n"
+-"              curl has connected this option is of no more use.  Since 7.32.0,\n"
+-"              this  option accepts decimal values, but the actual timeout will\n"
+-"              decrease in accuracy as the specified timeout increases in deci-\n"
+-, stdout);
+- fputs(
+-"              mal precision. See also the -m, --max-time option.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --create-dirs\n"
+-"              When  used  in  conjunction with the -o option, curl will create\n"
+-"              the necessary local directory hierarchy as needed.  This  option\n"
+-"              creates  the dirs mentioned with the -o option, nothing else. If\n"
+-"              the -o file name uses no dir or if the dirs it mentions  already\n"
+-, stdout);
+- fputs(
+-"              exist, no dir will be created.\n"
+-"\n"
+-"              To  create remote directories when using FTP or SFTP, try --ftp-\n"
+-"              create-dirs.\n"
+-"\n"
+-"       --crlf (FTP) Convert LF to CRLF in upload. Useful for MVS (OS/390).\n"
+-"\n"
+-"       --crlfile <file>\n"
+-"              (HTTPS/FTPS) Provide a file using PEM format with a  Certificate\n"
+-"              Revocation  List  that may specify peer certificates that are to\n"
+-"              be considered revoked.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"              (Added in 7.19.7)\n"
+-"       -d, --data <data>\n"
+-"              (HTTP) Sends the specified data in a POST request  to  the  HTTP\n"
+-"              server,  in  the  same  way  that a browser does when a user has\n"
+-"              filled in an HTML form and presses the submit button. This  will\n"
+-"              cause curl to pass the data to the server using the content-type\n"
+-, stdout);
+- fputs(
+-"              application/x-www-form-urlencoded.  Compare to -F, --form.\n"
+-"\n"
+-"              -d, --data is the same as  --data-ascii.  To  post  data  purely\n"
+-"              binary, you should instead use the --data-binary option. To URL-\n"
+-"              encode the value of a form field you may use --data-urlencode.\n"
+-"\n"
+-"              If any of these options is used more than once on the same  com-\n"
+-"              mand  line,  the  data  pieces specified will be merged together\n"
+-, stdout);
+- fputs(
+-"              with a separating  &-symbol.  Thus,  using  '-d  name=daniel  -d\n"
+-"              skill=lousy'  would  generate  a  post  chunk  that  looks  like\n"
+-"              'name=daniel&skill=lousy'.\n"
+-"\n"
+-"              If you start the data with the letter @, the rest  should  be  a\n"
+-"              file  name  to read the data from, or - if you want curl to read\n"
+-"              the data from stdin. Multiple files can also be specified. Post-\n"
+-, stdout);
+- fputs(
+-"              ing  data  from  a  file  named 'foobar' would thus be done with\n"
+-"              --data @foobar. When --data is told to read  from  a  file  like\n"
+-"              that, carriage returns and newlines will be stripped out.\n"
+-"\n"
+-"       -D, --dump-header <file>\n"
+-"              Write the protocol headers to the specified file.\n"
+-"\n"
+-"              This  option  is handy to use when you want to store the headers\n"
+-"              that an HTTP site sends to you. Cookies from the  headers  could\n"
+-, stdout);
+- fputs(
+-"              then  be  read  in  a  second  curl  invocation by using the -b,\n"
+-"              --cookie option! The -c, --cookie-jar option is however a better\n"
+-"              way to store cookies.\n"
+-"\n"
+-"              When  used  in FTP, the FTP server response lines are considered\n"
+-"              being \"headers\" and thus are saved there.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --data-ascii <data>\n"
+-"              See -d, --data.\n"
+-"\n"
+-"       --data-binary <data>\n"
+-, stdout);
+- fputs(
+-"              (HTTP) This posts data exactly as specified with no  extra  pro-\n"
+-"              cessing whatsoever.\n"
+-"\n"
+-"              If  you  start  the data with the letter @, the rest should be a\n"
+-"              filename.  Data is posted in a similar  manner  as  --data-ascii\n"
+-"              does,  except  that  newlines and carriage returns are preserved\n"
+-"              and conversions are never done.\n"
+-"\n"
+-"              If this option is used several times,  the  ones  following  the\n"
+-, stdout);
+- fputs(
+-"              first will append data as described in -d, --data.\n"
+-"\n"
+-"       --data-urlencode <data>\n"
+-"              (HTTP) This posts data, similar to the other --data options with\n"
+-"              the exception that this performs URL-encoding. (Added in 7.18.0)\n"
+-"              To be CGI-compliant, the <data> part should begin  with  a  name\n"
+-"              followed  by a separator and a content specification. The <data>\n"
+-"              part can be passed to curl using one of the following syntaxes:\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              content\n"
+-"                     This will make curl URL-encode the content and pass  that\n"
+-"                     on.  Just  be careful so that the content doesn't contain\n"
+-"                     any = or @ symbols, as that will  then  make  the  syntax\n"
+-"                     match one of the other cases below!\n"
+-"\n"
+-"              =content\n"
+-"                     This  will make curl URL-encode the content and pass that\n"
+-"                     on. The preceding = symbol is not included in the data.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              name=content\n"
+-"                     This will make curl URL-encode the content part and  pass\n"
+-"                     that  on.  Note that the name part is expected to be URL-\n"
+-"                     encoded already.\n"
+-"\n"
+-"              @filename\n"
+-"                     This will  make  curl  load  data  from  the  given  file\n"
+-"                     (including  any  newlines), URL-encode that data and pass\n"
+-"                     it on in the POST.\n"
+-"\n"
+-"              name@filename\n"
+-, stdout);
+- fputs(
+-"                     This will  make  curl  load  data  from  the  given  file\n"
+-"                     (including  any  newlines), URL-encode that data and pass\n"
+-"                     it on in the POST. The  name  part  gets  an  equal  sign\n"
+-"                     appended, resulting in name=urlencoded-file-content. Note\n"
+-"                     that the name is expected to be URL-encoded already.\n"
+-"\n"
+-"       --delegation LEVEL\n"
+-"              Set LEVEL to tell the server what it is allowed to delegate when\n"
+-, stdout);
+- fputs(
+-"              it comes to user credentials. Used with GSS/kerberos.\n"
+-"\n"
+-"              none   Don't allow any delegation.\n"
+-"\n"
+-"              policy Delegates  if  and only if the OK-AS-DELEGATE flag is set\n"
+-"                     in the Kerberos service ticket,  which  is  a  matter  of\n"
+-"                     realm policy.\n"
+-"\n"
+-"              always Unconditionally allow the server to delegate.\n"
+-"\n"
+-"       --digest\n"
+-"              (HTTP)  Enables HTTP Digest authentication. This is an authenti-\n"
+-, stdout);
+- fputs(
+-"              cation scheme that prevents the password from  being  sent  over\n"
+-"              the  wire in clear text. Use this in combination with the normal\n"
+-"              -u, --user option to  set  user  name  and  password.  See  also\n"
+-"              --ntlm, --negotiate and --anyauth for related options.\n"
+-"\n"
+-"              If  this  option  is  used  several times, only the first one is\n"
+-"              used.\n"
+-"\n"
+-"       --disable-eprt\n"
+-, stdout);
+- fputs(
+-"              (FTP) Tell curl to disable the use of the EPRT and LPRT commands\n"
+-"              when doing active FTP transfers. Curl will normally always first\n"
+-"              attempt to use EPRT, then LPRT before using PORT, but with  this\n"
+-"              option,  it  will  use PORT right away. EPRT and LPRT are exten-\n"
+-"              sions to the original FTP protocol, and  may  not  work  on  all\n"
+-"              servers, but they enable more functionality in a better way than\n"
+-, stdout);
+- fputs(
+-"              the traditional PORT command.\n"
+-"\n"
+-"              --eprt can be used to explicitly enable EPRT again and --no-eprt\n"
+-"              is an alias for --disable-eprt.\n"
+-"\n"
+-"              Disabling  EPRT only changes the active behavior. If you want to\n"
+-"              switch to passive mode you need to not  use  -P,  --ftp-port  or\n"
+-"              force it with --ftp-pasv.\n"
+-"\n"
+-"       --disable-epsv\n"
+-"              (FTP)  Tell  curl  to  disable  the use of the EPSV command when\n"
+-, stdout);
+- fputs(
+-"              doing passive FTP transfers. Curl  will  normally  always  first\n"
+-"              attempt  to  use EPSV before PASV, but with this option, it will\n"
+-"              not try using EPSV.\n"
+-"\n"
+-"              --epsv can be used to explicitly enable EPSV again and --no-epsv\n"
+-"              is an alias for --disable-epsv.\n"
+-"\n"
+-"              Disabling EPSV only changes the passive behavior. If you want to\n"
+-"              switch to active mode you need to use -P, --ftp-port.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"       --dns-interface <interface>\n"
+-"              Tell curl to send outgoing  DNS  requests  through  <interface>.\n"
+-"              This  option  is  a  counterpart  to --interface (which does not\n"
+-"              affect DNS). The supplied string must be an interface name  (not\n"
+-"              an address).\n"
+-"\n"
+-"              This  option  requires  that  libcurl  was built with a resolver\n"
+-"              backend that supports this operation. The c-ares backend is  the\n"
+-, stdout);
+- fputs(
+-"              only such one. (Added in 7.33.0)\n"
+-"\n"
+-"       --dns-ipv4-addr <ip-address>\n"
+-"              Tell curl to bind to <ip-address> when making IPv4 DNS requests,\n"
+-"              so that the DNS requests originate from this address. The  argu-\n"
+-"              ment should be a single IPv4 address.\n"
+-"\n"
+-"              This  option  requires  that  libcurl  was built with a resolver\n"
+-"              backend that supports this operation. The c-ares backend is  the\n"
+-, stdout);
+- fputs(
+-"              only such one.  (Added in 7.33.0)\n"
+-"\n"
+-"       --dns-ipv6-addr <ip-address>\n"
+-"              Tell curl to bind to <ip-address> when making IPv6 DNS requests,\n"
+-"              so that the DNS requests originate from this address. The  argu-\n"
+-"              ment should be a single IPv6 address.\n"
+-"\n"
+-"              This  option  requires  that  libcurl  was built with a resolver\n"
+-"              backend that supports this operation. The c-ares backend is  the\n"
+-, stdout);
+- fputs(
+-"              only such one.  (Added in 7.33.0)\n"
+-"\n"
+-"       --dns-servers <ip-address,ip-address>\n"
+-"              Set  the  list  of  DNS servers to be used instead of the system\n"
+-"              default.  The list of IP addresses should be separated with com-\n"
+-"              mas. Port numbers may also optionally be given as :<port-number>\n"
+-"              after each IP address.\n"
+-"\n"
+-"              This option requires that libcurl  was  built  with  a  resolver\n"
+-, stdout);
+- fputs(
+-"              backend  that supports this operation. The c-ares backend is the\n"
+-"              only such one.  (Added in 7.33.0)\n"
+-"\n"
+-"       -e, --referer <URL>\n"
+-"              (HTTP) Sends the \"Referrer Page\" information to the HTTP server.\n"
+-"              This can also be set with the -H, --header flag of course.  When\n"
+-"              used with -L, --location you can append \";auto\" to the --referer\n"
+-"              URL to make curl automatically set the previous URL when it fol-\n"
+-, stdout);
+- fputs(
+-"              lows a Location: header. The \";auto\" string can be  used  alone,\n"
+-"              even if you don't set an initial --referer.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       -E, --cert <certificate[:password]>\n"
+-"              (SSL)  Tells  curl  to use the specified client certificate file\n"
+-"              when getting a file with HTTPS, FTPS or another SSL-based proto-\n"
+-"              col.  The  certificate must be in PKCS#12 format if using Secure\n"
+-, stdout);
+- fputs(
+-"              Transport, or PEM format if using  any  other  engine.   If  the\n"
+-"              optional password isn't specified, it will be queried for on the\n"
+-"              terminal. Note that this option  assumes  a  \"certificate\"  file\n"
+-"              that  is  the  private  key and the private certificate concate-\n"
+-"              nated! See --cert and --key to specify them independently.\n"
+-"\n"
+-"              If curl is built against the NSS SSL library  then  this  option\n"
+-, stdout);
+- fputs(
+-"              can  tell curl the nickname of the certificate to use within the\n"
+-"              NSS database defined by the environment variable SSL_DIR (or  by\n"
+-"              default  /etc/pki/nssdb).  If  the  NSS PEM PKCS#11 module (lib-\n"
+-"              nsspem.so) is available then PEM files may  be  loaded.  If  you\n"
+-"              want to use a file from the current directory, please precede it\n"
+-"              with \"./\" prefix, in order to avoid confusion with  a  nickname.\n"
+-, stdout);
+- fputs(
+-"              If  the nickname contains \":\", it needs to be preceded by \"\\\" so\n"
+-"              that it is not recognized as password delimiter.  If  the  nick-\n"
+-"              name  contains \"\\\", it needs to be escaped as \"\\\\\" so that it is\n"
+-"              not recognized as an escape character.\n"
+-"\n"
+-"              (iOS and Mac OS X only) If curl is built against  Secure  Trans-\n"
+-"              port,  then  the  certificate string can either be the name of a\n"
+-, stdout);
+- fputs(
+-"              certificate/private key in the system or user keychain,  or  the\n"
+-"              path  to  a  PKCS#12-encoded certificate and private key. If you\n"
+-"              want to use a file from the current directory, please precede it\n"
+-"              with \"./\" prefix, in order to avoid confusion with a nickname.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --engine <name>\n"
+-"              Select  the  OpenSSL crypto engine to use for cipher operations.\n"
+-, stdout);
+- fputs(
+-"              Use --engine list  to  print  a  list  of  build-time  supported\n"
+-"              engines.  Note  that  not  all  (or  none) of the engines may be\n"
+-"              available at run-time.\n"
+-"\n"
+-"       --environment\n"
+-"              (RISC OS ONLY) Sets a range of environment variables, using  the\n"
+-"              names the -w option supports, to allow easier extraction of use-\n"
+-"              ful information after having run curl.\n"
+-"\n"
+-"       --egd-file <file>\n"
+-, stdout);
+- fputs(
+-"              (SSL) Specify the path name  to  the  Entropy  Gathering  Daemon\n"
+-"              socket.  The  socket  is  used to seed the random engine for SSL\n"
+-"              connections. See also the --random-file option.\n"
+-"\n"
+-"       --cert-type <type>\n"
+-"              (SSL) Tells curl what certificate type the provided  certificate\n"
+-"              is in. PEM, DER and ENG are recognized types.  If not specified,\n"
+-"              PEM is assumed.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --cacert <CA certificate>\n"
+-"              (SSL) Tells curl to use the specified certificate file to verify\n"
+-"              the  peer.  The  file  may contain multiple CA certificates. The\n"
+-"              certificate(s) must be in PEM format. Normally curl is built  to\n"
+-"              use a default file for this, so this option is typically used to\n"
+-"              alter that default file.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              curl recognizes the environment variable named  'CURL_CA_BUNDLE'\n"
+-"              if  it  is  set,  and uses the given path as a path to a CA cert\n"
+-"              bundle. This option overrides that variable.\n"
+-"\n"
+-"              The windows version of curl will automatically  look  for  a  CA\n"
+-"              certs file named 'curl-ca-bundle.crt', either in the same direc-\n"
+-"              tory as curl.exe, or in the Current Working Directory, or in any\n"
+-"              folder along your PATH.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              If  curl  is  built  against  the  NSS  SSL library, the NSS PEM\n"
+-"              PKCS#11 module (libnsspem.so) needs to  be  available  for  this\n"
+-"              option to work properly.\n"
+-"\n"
+-"              If this option is used several times, the last one will be used.\n"
+-"\n"
+-"       --capath <CA certificate directory>\n"
+-"              (SSL)  Tells  curl to use the specified certificate directory to\n"
+-"              verify the peer. Multiple paths can be  provided  by  separating\n"
+-, stdout);
+- fputs(
+-"              them with \":\" (e.g.  \"path1:path2:path3\"). The certificates must\n"
+-"              be in PEM format, and if curl  is  built  against  OpenSSL,  the\n"
+-"              directory  must  have  been processed using the c_rehash utility\n"
+-"              supplied with OpenSSL. Using --capath can allow  OpenSSL-powered\n"
+-"              curl  to  make  SSL-connections much more efficiently than using\n"
+-"              --cacert if the --cacert file contains many CA certificates.\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              If this option is set, the default capath value will be ignored,\n"
+-"              and if it is used several times, the last one will be used.\n"
+-"\n"
+-"       -f, --fail\n"
+-"              (HTTP)  Fail  silently (no output at all) on server errors. This\n"
+-"              is mostly done to better enable scripts etc to better deal  with\n"
+-"              failed  attempts.  In  normal cases when an HTTP server fails to\n"
+-"              deliver a document, it  returns  an  HTML  document  stating  so\n"
+-, stdout);
+- fputs(
+-"              (which  often  also describes why and more). This flag will pre-\n"
+-"              vent curl from outputting that and return error 22.\n"
+-"\n"
+-"              This method is not fail-safe and there are occasions where  non-\n"
+-"              successful  response  codes  will  slip through, especially when\n"
+-"              authentication is involved (response codes 401 and 407).\n"
+-"\n"
+-"       -F, --form <name=content>\n"
+-"              (HTTP) This lets curl emulate a filled-in form in which  a  user\n"
+-, stdout);
+- fputs(
+-"              has  pressed  the  submit  button. This causes curl to POST data\n"
+-"              using the  Content-Type  multipart/form-data  according  to  RFC\n"
+-"              2388.  This  enables uploading of binary files etc. To force the\n"
+-"              'content' part to be a file, prefix the  file  name  with  an  @\n"
+-"              sign.  To just get the content part from a file, prefix the file\n"
+-"              name with the symbol <. The difference between @ and <  is  then\n"
+-, stdout);
+- fputs(
+-"              that  @  makes a file get attached in the post as a file upload,\n"
+-"              while the < makes a text field and just  get  the  contents  for\n"
+-"              that text field from a file.\n"
+-"\n"
+-"              Example,  to send your password file to the server, where 'pass-\n"
+-"              word' is the name of the form-field to which /etc/passwd will be\n"
+-"              the input:\n"
+-"\n"
+-"              curl -F password=@/etc/passwd www.mypasswords.com\n"
+-"\n"
+-, stdout);
+- fputs(
+-"              To read content from stdin instead of a file, use - as the file-\n"
+-"              name. This goes for both @ and < constructs.\n"
+-"\n"
+-"              You can also  tell  curl  what  Content-Type  to  use  by  using\n"
+-"              'type=', in a manner similar to:\n"
+-"\n"
+-"              curl -F \"web=@index.html;type=text/html\" url.com\n"
+-"\n"
+-"              or\n"
+-"\n"
+-"              curl -F \"name=daniel;type=text/foo\" url.com\n"
+-"\n"
+-"              You  can  also explicitly change the name field of a file upload\n"
+-, stdout);
+- fputs(
+-"              part by setting filename=, like this:\n"
+-"\n"
+-"              curl -F \"file=@localfile;filename=nameinpost\" url.com\n"
+-"\n"
+-"              If filename/path contains ',' or ';', it must be quoted by  dou-\n"
+-"              ble-quotes like:\n"
+-"\n"
+-"              curl -F \"file=@\\\"localfile\\\";filename=\\\"nameinpost\\\"\" url.com\n"
+-"\n"
+-"              or\n"
+-"\n"
+-"              curl -F 'file=@\"localfile\";filename=\"nameinpost\"' url.com\n"
+-"\n"
+-"              Note  that  if  a  filename/path is quoted