https://llvm.org/bugs/show_bug.cgi?id=31438

            Bug ID: 31438
           Summary: lldb trunk r290074 fails to compile on Mountain Lion
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: lldb-...@lists.llvm.org
          Reporter: jerem...@apple.com
                CC: llvm-bugs@lists.llvm.org
    Classification: Unclassified

lldb trunk r290074 fails to compile on Mountain Lion.  I'm not sure the last
time this built on 10.8:

/opt/local/var/macports/build/_Users_jeremy_src_macports_macports-ports_lang_llvm-devel/lldb-devel/work/trunk/tools/lldb/tools/debugserver/source/MacOSX/MachTask.mm:437:18:
error: no member named 'external_page_count' in 'vm_statistics64'
          vminfo.external_page_count - vminfo.purgeable_count;
          ~~~~~~ ^
1 error generated.

---

Fallout from:

commit a015ff55b22de49a8805ab5c368e5eca6a20d748
Author: Kate Stone <katherine.st...@apple.com>
Date:   Tue Sep 6 20:57:50 2016 +0000

    *** This commit represents a complete reformatting of the LLDB source code
    *** to conform to clang-format’s LLVM style.  This kind of mass change has
    *** two obvious implications:

    Firstly, merging this particular commit into a downstream fork may be a
huge
    effort.  Alternatively, it may be worth merging all changes up to this
commit,
    performing the same reformatting operation locally, and then discarding the
    merge for this particular commit.  The commands used to accomplish this
    reformatting were as follows (with current working directory as the root of
    the repository):

        find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname
"*.mm" \) -exec clang-format -i {} +
        find . -iname "*.py" -exec autopep8 --in-place --aggressive
--aggressive {} + ;

    The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

    Secondly, “blame” style tools will generally point to this commit instead
of
    a meaningful prior commit.  There are alternatives available that will
attempt
    to look through this change and find the appropriate prior commit.  YMMV.



    git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@280751
91177308-0d34-0410-b5e6-96231b3b80d8

---

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to