included from Makefile.inc

buildconf.bat is only for CVS tree builds.

archives. Used as a sentinel file in buildconf.bat to differentiate CVS builds.

the makefile cannot depend on it

Disable the '-export-symbols-regex' to discard this as the origin
of link failures related with shared libraries and non-GNU linkers.

reporting package version in parentheses which confused this script.

Remove debug tracing used to debug this.

- Added some cmake docs and fixed socklen_t in the build.

  broken since 7.19.0

debug test a non-greedy pattern

Add some debug tracing

remove the ofending regexp

remove line not intended to be committed

attempt to fix regex

Adjusted libtool version parsing due to libtool --version now also
reporting package name in parentheses which confused this script.

Revert delegating c-ares linking magic on libtool and auto-makefiles when using
the uninstalled c-ares libtool archive built from the CVS embedded tree.

This embedded c-ares linking is again handled from the configure script.

c-ares Makefile.am back to using $(top_builddir) for *_LDADD

installed in the subdirectory at different stages. With some versions it is
installed when libtoolize finishes, but with others it is not installed
until automake has finished.

So we can not attempt to use config.guess until the very last buildconf stage.

  is almost always a VERY BAD IDEA. Yet there are still apps out there doing
  this, and now recently it triggered a bug/side-effect in libcurl as when
  libcurl sends a POST or PUT with NTLM, it sends an empty post first when it
  knows it will just get a 401/407 back. If the app then replaced the
  Content-Length header, it caused the server to wait for input that libcurl
  wouldn't send. Aaron Oneal reported this problem in bug report #2799008
  http://curl.haxx.se/bug/view.cgi?id=2799008) and helped us verify the fix.

Yet unknown error might leave libtool-like files in source directory.

This can be done now that no file with such name exists in CVS tree.