Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 663378 - net-irc/quassel-0.13_rc1 with CMAKE_MAKEFILE_GENERATOR=ninja build.ninja:3891: multiple rules generate quasselclient [-w dupbuild=err]
Summary: net-irc/quassel-0.13_rc1 with CMAKE_MAKEFILE_GENERATOR=ninja build.ninja:3891...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Patrick Lauer
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: ninja-porting
  Show dependency tree
 
Reported: 2018-08-11 18:51 UTC by Mike Gilbert
Modified: 2019-05-14 16:58 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Gilbert gentoo-dev 2018-08-11 18:51:46 UTC
>>> Working in BUILD_DIR: "/x/portage/net-irc/quassel-0.13_rc1/work/quassel-0.13_rc1_build"
ninja -v -j6 -l0
ninja: error: build.ninja:3891: multiple rules generate quasselclient [-w dupbuild=err]
Comment 1 Mike Gilbert gentoo-dev 2018-08-11 18:55:05 UTC
I think this OUTPUT_PATH property causes cmake to emit two targets that refer to the same file.

https://github.com/quassel/quassel/blob/0.13-rc1/src/CMakeLists.txt#L61
Comment 2 Franz Trischberger 2018-09-06 12:28:50 UTC
Could you re-check with =ninja-1.8.2? This looks similar to https://bugs.gentoo.org/663384.
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2018-10-20 12:31:16 UTC
Could you please test 0.13_rc2

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=25f8b856e18bb98d4e5c4e6f1755c17e16d4de6f
Comment 4 Johannes Huber (RETIRED) gentoo-dev 2019-05-01 09:41:31 UTC
(In reply to Johannes Huber from comment #3)
> Could you please test 0.13_rc2
> 
> https://gitweb.gentoo.org/repo/gentoo.git/commit/
> ?id=25f8b856e18bb98d4e5c4e6f1755c17e16d4de6f

How about 0.13.1?
Comment 5 Mike Gilbert gentoo-dev 2019-05-01 13:27:26 UTC
This has been fixed upstream for quite some time. Also, a change was applied to ninja to fix/workaround the issue on that end.