...at your own risk.  cURL has had some serious security issues over
the years, so if you're using an ancient version, I hope that you're
receiving security patches from your vendor.

The version set here is to accommodate CentOS 6.

FS-353

FS-353

This purges libcurl from our tree and requires it to be present on the
system for building and running FreeSWITCH.

FS-353

These modules use curl and we'll be adding in some bits to the
CPPFLAGS.

Too much was staged accidentally on that last commit.

This reverts commit f1126272.

Mike and Seven said this is desirable.

FS-353: allow people to use 5 year old and with known segfault issues pcre because centos6 can't seem to use a lib less that 5 years old, use with older libs at your own risk

We don't currently have a use-case for this, but we'd been
distributing this file in packaging as part of libfreeswitch-dev.

We check whether the dir is there before trying to bootstrap, so it
didn't do any harm, but they shouldn't be there.

We love mod_v8 and Peter for making it work so well and in so many
places.

But it still doesn't build on as many platforms as the rest of
FreeSWITCH, and it requires using getlib on a huge library while we're
currently trying to pull libraries out of tree and reduce our
dependence on getlib.  We need to work on getting distributions to
push updated versions of libv8.

libspeex and libspeexdsp are now hard system dependencies for
building and running FreeSWITCH.

FS-353

FS-353
Signed-off-by: Travis Cross <tc@traviscross.com>

libpcre is now a hard system dependency for building and running
FreeSWITCH.

FS-353

FS-353
Signed-off-by: Travis Cross <tc@traviscross.com>

FS-6387 don't fail if your openssl package has been compiled without EC support...LOOKING AT YOU GENTOO

We'll add this back when the build issues with it get worked out.
See FS-6385.

fix perldir to at least point to install the same place as the code looks for it.  Note, on fhs type builds, where prefix is /usr, these files are going to go into /usr/perl, which probably isn't right, but thats where the code looks too, we should do something better for builds that are not in the prefix

Now that we're using AM_SILENT_RULES this needs to be set so we can
see what's going on in our build logs.

Autogenerated bits of the code warn when building which would
otherwise break the build.