[LLVMbugs] [Bug 14709] New: Build from source instructions lacking

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon Dec 24 18:34:04 PST 2012


             Bug #: 14709
           Summary: Build from source instructions lacking
           Product: Build scripts
           Version: 3.2
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Makefiles
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: rmann at latencyzero.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

I just downloaded the LLVM 3.2 source tarball, wanting to build LLVM for the
Raspberry Pi (Raspbian). Unfortunately, I really can't tell how to get started
with the build.

The README.txt document refers to docs/index.html. But docs/ uses Sphinx, and
there is no pre-generated HTML.

I looked at LLVMBuild.txt, but it just talks about how the source is organized
to support the LLVM build conventions.

I looked at the LLVM Makefile guide, which suggests you're not using autoconf
(which I took to mean ./configure wasn't used, either), or any other build
system (like CMake). But I see both autoconf and CMake stuff in the distro.

Simply issuing "make" doesn't build anything; it acts like it needs configure
to run first. I looked at the FAQ, and the first question has to do with
running configure. So, I run configure, which seems to run okay, followed by
make, which seems to run okay.

A simple text file at the root of the source distro, with simple build
instructions, would be nice. It would've saved me several minutes of searching
and wondering and nearly abandoning the thought of using LLVM for my little
interpreter project.

I'm not sure if it's possible to cross-compile llvm. I did find a
"HowToBuildOnARM.rst" document, although like many such things, it assumes a
certain amount of experience.

Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the llvm-bugs mailing list