Michael Giuffrida
2018-11-29 23:34:07 UTC
I'm encountering a new issue when trying to build Chromium OS: file
collisions from the llvm package with itself.
For instance, setup_board fails to emerge llvm:
$ ./setup_board --board=$BOARD --force
due to file collisions. Per the instructions in the output, I've identified
that a different revision of llvm owns these files:
$ portageq owners / /usr/include/clang/Lex/Lexer.h
sys-devel/llvm-8.0_pre339409_p20180926-r3
/usr/include/clang/Lex/Lexer.h
The output for setup_board is below. Why is it trying to emerge llvm r6
without removing llvm r3?
=== Start output for job llvm-8.0_pre339409_p20180926-r6 (0m7.6s) ===
llvm-8.0_pre339409_p20180926-r6: >>> Running pre-merge checks for sys-devel/llvm-8.0_pre339409_p20180926-r6
llvm-8.0_pre339409_p20180926-r6: * llvm-8.0_pre339409_p20180926-r6.tbz2 MD5 SHA1 size ;-) ... [ ok ]
llvm-8.0_pre339409_p20180926-r6: >>> Emerging binary (1 of 1) sys-devel/llvm-8.0_pre339409_p20180926-r6::chromiumos
llvm-8.0_pre339409_p20180926-r6: * llvm-8.0_pre339409_p20180926-r6.tbz2 MD5 SHA1 size ;-) ... [ ok ]
llvm-8.0_pre339409_p20180926-r6: * Running stacked hooks for pre_pkg_setup
llvm-8.0_pre339409_p20180926-r6: * sysroot_build_bin_dir ...
llvm-8.0_pre339409_p20180926-r6: [ ok ]
llvm-8.0_pre339409_p20180926-r6: * Running stacked hooks for post_pkg_setup
llvm-8.0_pre339409_p20180926-r6: * python_eclass_hack ...
llvm-8.0_pre339409_p20180926-r6: [ ok ]
llvm-8.0_pre339409_p20180926-r6: pbzip2: *WARNING: Trailing garbage after EOF ignored!
llvm-8.0_pre339409_p20180926-r6: >>> Installing (1 of 1) sys-devel/llvm-8.0_pre339409_p20180926-r6::chromiumos
llvm-8.0_pre339409_p20180926-r6: * This package will overwrite one or more files that may belong to other
llvm-8.0_pre339409_p20180926-r6: * packages (see list below). You can use a command such as `portageq
llvm-8.0_pre339409_p20180926-r6: * owners / <filename>` to identify the installed package that owns a
llvm-8.0_pre339409_p20180926-r6: * file. If portageq reports that only one package owns a file then do
llvm-8.0_pre339409_p20180926-r6: * NOT file a bug report. A bug report is only useful if it identifies at
llvm-8.0_pre339409_p20180926-r6: * least two or more packages that are known to install the same file(s).
llvm-8.0_pre339409_p20180926-r6: * If a collision occurs and you can not explain where the file came from
llvm-8.0_pre339409_p20180926-r6: * then you should simply ignore the collision since there is not enough
llvm-8.0_pre339409_p20180926-r6: * information to determine if a real problem exists. Please do NOT file
llvm-8.0_pre339409_p20180926-r6: * a bug report at http://bugs.gentoo.org unless you report exactly which
llvm-8.0_pre339409_p20180926-r6: * two packages install the same file(s). See
llvm-8.0_pre339409_p20180926-r6: * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
llvm-8.0_pre339409_p20180926-r6: * solve the problem. And once again, please do NOT file a bug report
llvm-8.0_pre339409_p20180926-r6: * unless you have completely understood the above message.
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Detected file collision(s):
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMTActions.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMT.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/FileRemapper.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Preprocessor.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Lexer.h
<nine thousand files later...>
llvm-8.0_pre339409_p20180926-r6: * Searching all installed packages for file collisions...
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Press Ctrl-C to Stop
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * sys-devel/llvm-8.0_pre339409_p20180926-r3:8::chromiumos
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMT.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMTActions.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/FileRemapper.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/CodeCompletionHandler.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/DirectoryLookup.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/LexDiagnostic.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Lexer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/LiteralSupport.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MacroArgs.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MacroInfo.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ModuleLoader.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ModuleMap.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MultipleIncludeOpt.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PTHManager.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PreprocessingRecord.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Preprocessor.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PreprocessorLexer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ScratchBuffer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Token.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/TokenConcatenation.h
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Package 'sys-devel/llvm-8.0_pre339409_p20180926-r6' NOT merged due to
llvm-8.0_pre339409_p20180926-r6: * file collisions. If necessary, refer to your elog messages for the
llvm-8.0_pre339409_p20180926-r6: * whole content of the above message.
=== Complete: job llvm-8.0_pre339409_p20180926-r6 (0m7.2s) ===
collisions from the llvm package with itself.
For instance, setup_board fails to emerge llvm:
$ ./setup_board --board=$BOARD --force
due to file collisions. Per the instructions in the output, I've identified
that a different revision of llvm owns these files:
$ portageq owners / /usr/include/clang/Lex/Lexer.h
sys-devel/llvm-8.0_pre339409_p20180926-r3
/usr/include/clang/Lex/Lexer.h
The output for setup_board is below. Why is it trying to emerge llvm r6
without removing llvm r3?
=== Start output for job llvm-8.0_pre339409_p20180926-r6 (0m7.6s) ===
llvm-8.0_pre339409_p20180926-r6: >>> Running pre-merge checks for sys-devel/llvm-8.0_pre339409_p20180926-r6
llvm-8.0_pre339409_p20180926-r6: * llvm-8.0_pre339409_p20180926-r6.tbz2 MD5 SHA1 size ;-) ... [ ok ]
llvm-8.0_pre339409_p20180926-r6: >>> Emerging binary (1 of 1) sys-devel/llvm-8.0_pre339409_p20180926-r6::chromiumos
llvm-8.0_pre339409_p20180926-r6: * llvm-8.0_pre339409_p20180926-r6.tbz2 MD5 SHA1 size ;-) ... [ ok ]
llvm-8.0_pre339409_p20180926-r6: * Running stacked hooks for pre_pkg_setup
llvm-8.0_pre339409_p20180926-r6: * sysroot_build_bin_dir ...
llvm-8.0_pre339409_p20180926-r6: [ ok ]
llvm-8.0_pre339409_p20180926-r6: * Running stacked hooks for post_pkg_setup
llvm-8.0_pre339409_p20180926-r6: * python_eclass_hack ...
llvm-8.0_pre339409_p20180926-r6: [ ok ]
llvm-8.0_pre339409_p20180926-r6: pbzip2: *WARNING: Trailing garbage after EOF ignored!
llvm-8.0_pre339409_p20180926-r6: >>> Installing (1 of 1) sys-devel/llvm-8.0_pre339409_p20180926-r6::chromiumos
llvm-8.0_pre339409_p20180926-r6: * This package will overwrite one or more files that may belong to other
llvm-8.0_pre339409_p20180926-r6: * packages (see list below). You can use a command such as `portageq
llvm-8.0_pre339409_p20180926-r6: * owners / <filename>` to identify the installed package that owns a
llvm-8.0_pre339409_p20180926-r6: * file. If portageq reports that only one package owns a file then do
llvm-8.0_pre339409_p20180926-r6: * NOT file a bug report. A bug report is only useful if it identifies at
llvm-8.0_pre339409_p20180926-r6: * least two or more packages that are known to install the same file(s).
llvm-8.0_pre339409_p20180926-r6: * If a collision occurs and you can not explain where the file came from
llvm-8.0_pre339409_p20180926-r6: * then you should simply ignore the collision since there is not enough
llvm-8.0_pre339409_p20180926-r6: * information to determine if a real problem exists. Please do NOT file
llvm-8.0_pre339409_p20180926-r6: * a bug report at http://bugs.gentoo.org unless you report exactly which
llvm-8.0_pre339409_p20180926-r6: * two packages install the same file(s). See
llvm-8.0_pre339409_p20180926-r6: * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
llvm-8.0_pre339409_p20180926-r6: * solve the problem. And once again, please do NOT file a bug report
llvm-8.0_pre339409_p20180926-r6: * unless you have completely understood the above message.
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Detected file collision(s):
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMTActions.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMT.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/FileRemapper.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Preprocessor.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Lexer.h
<nine thousand files later...>
llvm-8.0_pre339409_p20180926-r6: * Searching all installed packages for file collisions...
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Press Ctrl-C to Stop
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * sys-devel/llvm-8.0_pre339409_p20180926-r3:8::chromiumos
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMT.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/ARCMTActions.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/ARCMigrate/FileRemapper.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/CodeCompletionHandler.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/DirectoryLookup.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/LexDiagnostic.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Lexer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/LiteralSupport.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MacroArgs.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MacroInfo.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ModuleLoader.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ModuleMap.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/MultipleIncludeOpt.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PTHManager.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PreprocessingRecord.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Preprocessor.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/PreprocessorLexer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/ScratchBuffer.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/Token.h
llvm-8.0_pre339409_p20180926-r6: * /usr/include/clang/Lex/TokenConcatenation.h
llvm-8.0_pre339409_p20180926-r6: *
llvm-8.0_pre339409_p20180926-r6: * Package 'sys-devel/llvm-8.0_pre339409_p20180926-r6' NOT merged due to
llvm-8.0_pre339409_p20180926-r6: * file collisions. If necessary, refer to your elog messages for the
llvm-8.0_pre339409_p20180926-r6: * whole content of the above message.
=== Complete: job llvm-8.0_pre339409_p20180926-r6 (0m7.2s) ===
--
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/67093637-91ea-4e12-a29b-9fe95769b44f%40chromium.org.
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/67093637-91ea-4e12-a29b-9fe95769b44f%40chromium.org.