llvm-6502/autoconf
Peter Zotov 47f88b5bdf [OCaml] [autoconf] Migrate to ocamlfind.
This commit updates the OCaml bindings and tests to use ocamlfind.
The bindings are migrated in order to use ctypes, which are now
required for MCJIT-backed Llvm_executionengine.
The tests are migrated in order to use OUnit and to verify that
the distributed META.llvm allows to build working executables.

Every OCaml toolchain invocation is now chained through ocamlfind,
which (in theory) allows to cross-compile the OCaml bindings.

The configure script now checks for ctypes (>= 0.2.3) and
OUnit (>= 2). The code depending on these libraries will be added
later. The configure script does not check the package versions
in order to keep changes less invasive.

Additionally, OCaml bindings will now be automatically enabled
if ocamlfind is detected on the system, rather than ocamlc, as it
was before.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@220899 91177308-0d34-0410-b5e6-96231b3b80d8
2014-10-30 08:29:45 +00:00
..
m4 Remove path_tclsh.m4. 2014-06-02 12:54:32 +00:00
AutoRegen.sh Drop libtool from llvm. 2014-02-28 18:17:54 +00:00
config.guess Add aarch64 to config.guess 2014-02-25 09:30:54 +00:00
config.sub Recognize aarch64_be as valid architecture. 2014-10-06 23:05:04 +00:00
configure.ac [OCaml] [autoconf] Migrate to ocamlfind. 2014-10-30 08:29:45 +00:00
ExportMap.map
install-sh
LICENSE.TXT
missing
mkinstalldirs
README.TXT Now that we don't use libtool, we don't need to upgrade it :-) 2014-03-05 22:45:14 +00:00

Upgrading autoconf
===============================================================================

If you are in the mood to upgrade autoconf, you should:

 1. Consider not upgrading.
 2. No really, this is a hassle, you don't want to do it.
 3. Get the new version of autoconf and put it in <SRC>
 4. configure/build/install autoconf with --prefix=<PFX>
 5. Run autoupdate on all the m4 macros in llvm/autoconf/m4
 6. Run autoupdate on llvm/autoconf/configure.ac
 7. Regenerate configure script with AutoRegen.sh
 8. If there are any warnings from AutoRegen.sh, fix them and go to step 7.
 9. Test, test, test.