Bug#889035: src:llvm-toolchain-5.0: New symbols appeared in the symbols file

Andreas Boll andreas.boll.dev at gmail.com
Thu Feb 1 11:23:33 UTC 2018


Package: src:llvm-toolchain-5.0
Version: 1:5.0.1-2
Severity: normal

Dear Maintainer,

There are new symbols exported by libclang1-5.0. Please update the symbols
file.

New symbols: (see also build log [1])

--- new_symbol_file (libclang1-5.0_1:5.0.1-2_i386)
+++ dpkg-gensymbolsuaN6L9	2017-12-22 22:00:39.778307536 +0000
@@ -62,12 +62,14 @@
  clang_Cursor_isAnonymous at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isBitField at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isDynamicCall at LLVM_5.0 1:5.0~svn298832-1~
+ clang_Cursor_isExternalSymbol at LLVM_5.0 1:5.0.1-2
  clang_Cursor_isFunctionInlined at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isMacroBuiltin at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isMacroFunctionLike at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isNull at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isObjCOptional at LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isVariadic at LLVM_5.0 1:5.0~svn298832-1~
+ clang_EnumDecl_isScoped at LLVM_5.0 1:5.0.1-2
  clang_EvalResult_dispose at LLVM_5.0 1:5.0~svn298832-1~
  clang_EvalResult_getAsDouble at LLVM_5.0 1:5.0~svn298832-1~
  clang_EvalResult_getAsInt at LLVM_5.0 1:5.0~svn298832-1~
@@ -187,6 +189,7 @@
  clang_findReferencesInFileWithBlock at LLVM_5.0 1:5.0~svn298832-1~
  clang_formatDiagnostic at LLVM_5.0 1:5.0~svn298832-1~
  clang_free at LLVM_5.0 1:5.0~svn298832-1~
+ clang_getAddressSpace at LLVM_5.0 1:5.0.1-2
  clang_getAllSkippedRanges at LLVM_5.0 1:5.0~svn302377-1~
  clang_getArgType at LLVM_5.0 1:5.0~svn298832-1~
  clang_getArrayElementType at LLVM_5.0 1:5.0~svn298832-1~
@@ -213,6 +216,7 @@
  clang_getCursorCompletionString at LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorDefinition at LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorDisplayName at LLVM_5.0 1:5.0~svn298832-1~
+ clang_getCursorExceptionSpecificationType at LLVM_5.0 1:5.0.1-2
  clang_getCursorExtent at LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorKind at LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorKindSpelling at LLVM_5.0 1:5.0~svn298832-1~
@@ -249,6 +253,7 @@
  clang_getEnumConstantDeclUnsignedValue at LLVM_5.0 1:5.0~svn298832-1~
  clang_getEnumConstantDeclValue at LLVM_5.0 1:5.0~svn298832-1~
  clang_getEnumDeclIntegerType at LLVM_5.0 1:5.0~svn298832-1~
+ clang_getExceptionSpecificationType at LLVM_5.0 1:5.0.1-2
  clang_getExpansionLocation at LLVM_5.0 1:5.0~svn298832-1~
  clang_getFieldDeclBitWidth at LLVM_5.0 1:5.0~svn298832-1~
  clang_getFile at LLVM_5.0 1:5.0~svn298832-1~
@@ -299,6 +304,7 @@
  clang_getTypeKindSpelling at LLVM_5.0 1:5.0~svn298832-1~
  clang_getTypeSpelling at LLVM_5.0 1:5.0~svn298832-1~
  clang_getTypedefDeclUnderlyingType at LLVM_5.0 1:5.0~svn298832-1~
+ clang_getTypedefName at LLVM_5.0 1:5.0.1-2
  clang_hashCursor at LLVM_5.0 1:5.0~svn298832-1~
  clang_indexLoc_getCXSourceLocation at LLVM_5.0 1:5.0~svn298832-1~
  clang_indexLoc_getFileLocation at LLVM_5.0 1:5.0~svn298832-1~
@@ -344,6 +350,7 @@
  clang_reparseTranslationUnit at LLVM_5.0 1:5.0~svn298832-1~
  clang_saveTranslationUnit at LLVM_5.0 1:5.0~svn298832-1~
  clang_sortCodeCompletionResults at LLVM_5.0 1:5.0~svn298832-1~
+ clang_suspendTranslationUnit at LLVM_5.0 1:5.0.1-2
  clang_toggleCrashRecovery at LLVM_5.0 1:5.0~svn298832-1~
  clang_tokenize at LLVM_5.0 1:5.0~svn298832-1~
  clang_visitChildren at LLVM_5.0 1:5.0~svn298832-1~


For easier detection of such issues I'd recommend bumping the dpkg-gensymbols
checker level to 4. This will cause the build to fail if there are any symbol
changes (added or removed).

e.g.
- dh_makeshlibs -plibclang1-5.0 -V"libclang1-5.0 (>= 1:5.0~svn298832-1~)"
+ dh_makeshlibs -plibclang1-5.0 -V"libclang1-5.0 (>= 1:5.0~svn298832-1~)" -- -c4


Thanks,
Andreas

[1] https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-5.0&arch=i386&ver=1%3A5.0.1-2&stamp=1513980534&raw=0



More information about the Pkg-llvm-team mailing list