From: Misha Brukman Date: Wed, 9 Feb 2005 22:38:47 +0000 (+0000) Subject: * Use an HTML list
    instead of custom superscripts in the platform notes X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=6d8e153e421ad9f5ecde60ce70723ecdd3c20705;p=oota-llvm.git * Use an HTML list
      instead of custom superscripts in the platform notes * Reorder software requirements list to show relative importance * Use superscripts for footnotes in software list rather than "Note 1" * Use new doc_notes class to separate footnotes from main doc text git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@20098 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 7a5fdf5408d..e49608a624d 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -274,28 +274,25 @@ software you will need.

      Notes:

      -
      -1 - Code generation supported for Pentium processors and up
      -2 - Code generation supported for 32-bit ABI only
      -3 - No native code generation
      -4 - Build is not complete: one or more tools don't link
      -5 - The GCC-based C/C++ frontend does not build
      -6 - The port is done using the MSYS shell. +
      +
        +
      1. Code generation supported for Pentium processors and +up
        2. +
      2. Code generation supported for 32-bit ABI only
        3. +
      3. No native code generation
        4. +
      4. Build is not complete: one or more tools don't link
        5. +
      5. The GCC-based C/C++ frontend does not build
        6. +
      6. The port is done using the MSYS shell. Download and install bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source, if necessary. If you need to create a library for an MS DLL, do the following: -
          +
          • pexports /C/WINNT/SYSTEM32/file.dll | sed "s/^_//" > /C/MinGW/lib/file.def
          • Edit file and append @<ordinal> to the missing function name
          • dlltool.exe -k -d /C/MinGW/lib/file.def -l /C/MinGW/lib/libfile.a.
            • +
      @@ -338,7 +335,7 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

      GCC 3.4.2 - C/C++ compiler (Note 3) + C/C++ compiler1 @@ -353,78 +350,80 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

      YACC compiler + + CVS + ≥1.11 + CVS access to LLVM2 + + DejaGnu 1.4.2 - Automated test suite (Note 2) + Automated test suite3 tcl 8.3, 8.4 - Automated test suite (Note 2) + Automated test suite3 expect 5.38.0 - Automated test suite (Note 2) + Automated test suite3 + + + + perl + ≥5.6.0 + Nightly tester, utilities GNU M4 1.4 - Macro processor for configuration (Note 1) + Macro processor for configuration4 GNU Autoconf 2.59 - Configuration script builder (Note 1) + Configuration script builder4 GNU Automake 1.9.2 - aclocal macro generator (Note 1) - - - - perl - ≥5.6.0 - Nightly tester, utilities + aclocal macro generator4 libtool 1.5.10 - Shared library manager (Note 1) - - - - CVS - ≥1.11 - CVS access to LLVM (Note 4) + Shared library manager4 -

      Notes:

      +

      Notes:

      +
        -
      1. If you want to make changes to the configure scripts, - you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4 - or higher). You will also need automake (1.9.2). We only use aclocal - from that package.
        2. -
      2. Only needed if you want to run the automated test - suite in the test directory.
        3. -
      3. Only the C and C++ languages are needed so there's no +
      4. Only the C and C++ languages are needed so there's no need to build the other languages for LLVM's purposes. See - below for specific version info. -
        5. -
      5. You only need CVS if you intend to build from the + below for specific version info.
        6. +
      6. You only need CVS if you intend to build from the latest LLVM sources. If you're working from a release distribution, you don't need CVS.
        7. +
      7. Only needed if you want to run the automated test + suite in the llvm/test directory.
        8. +
      8. If you want to make changes to the configure scripts, + you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4 + or higher). You will also need automake (1.9.2). We only use aclocal + from that package.
      +
      +

      Additionally, your compilation host is expected to have the usual plethora of Unix utilities. Specifically: