llvm-6502/autoconf
Rafael Espindola 9802a6cbdc Remove projects/sample.
As an example that was not actually being used, it suffered from a slow bitrot.

The two main issues with it were that it had no cmake support and
included a copy of the autoconf directory. The reality is that
autoconf is not easily composable. The lack of composabilty is why we
have clang options in llvm's configure. Suggesting that users include
a copy of autoconf/ in their projects seems a bad idea.

We are also in the process of switching to cmake, so pushing autoconf
to new project is probably not what we want.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@203728 91177308-0d34-0410-b5e6-96231b3b80d8
2014-03-12 22:40:22 +00:00
..
m4 Drop libtool from llvm. 2014-02-28 18:17:54 +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 Add AArch64 as an experimental target. 2013-01-31 12:12:40 +00:00
configure.ac Remove projects/sample. 2014-03-12 22:40:22 +00:00
ExportMap.map fix PR5954, patch by Roman Divacky. 2010-02-24 22:33:41 +00:00
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.