llvm.org GIT mirror llvm / 0a1f67a
Added information on why someone would want to build the GCC front end. Added a link to this information from the Getting Started Guide. Changed the word "wicked" to "elite." The original sounds much cooler, but I fear the PR police when I take off my tinfoil hat. git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_1@9454 91177308-0d34-0410-b5e6-96231b3b80d8 John Criswell 15 years ago
2 changed file(s) with 18 addition(s) and 3 deletion(s). Raw diff Collapse all Expand all
1414 C/C++ front-end, based on GCC 3.4, from source.

1515
1616

NOTE: This is currently a somewhat fragile, error-prone

17 process, and you should only try to do it if (A) you really, really,
18 really can't use the binaries we distribute, and (B) you are a wicked
19 good GCC hacker.

17 process, and you should only try to do it if
18
19
  • (A) you really, really, really can't use the binaries we distribute
  • 20
  • (B) you need GCC to fix some of the header files on your system
  • 21
  • (C) you are an elite GCC hacker.

  • 22
    2023
    2124

    We welcome patches to help make this process simpler.

    2225
    406406 ./fixheaders
    407407
    408408
    409

    410 The binary versions of the GCC front end may not suit all of your needs.
    411 For example, the binary distribution may include an old version of a system
    412 header file, not "fix" a header file that needs to be fixed for GCC, or it
    413 may be linked with libraries not available on your system.
    414

    415
    416

    417 In cases like these, you may want to try
    418 building the GCC front end from source.
    419 This is not for the faint of heart, so be forewarned.
    420

    409421
    410422

    Local LLVM Configuration

    411423