Bug 1309055 - [clang] CommandLine Error: Option 'track-memory' registered more than once!
[clang] CommandLine Error: Option 'track-memory' registered more than once!
Product: Fedora
Classification: Fedora
Component: clang (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
: 1309535 1311489 (view as bug list)
Depends On:
Blocks: 1307869 1309295
  Show dependency treegraph
Reported: 2016-02-16 13:11 EST by Joachim Frieben
Modified: 2017-02-14 18:50 EST (History)
8 users (show)

See Also:
Fixed In Version: clang-3.8.0-0.3.fc24
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-24 20:10:40 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sample C++ program (557 bytes, text/x-csrc)
2016-02-16 13:11 EST, Joachim Frieben
no flags Details

  None (edit)
Description Joachim Frieben 2016-02-16 13:11:19 EST
Created attachment 1127662 [details]
Sample C++ program

Description of problem:
For the current Fedora development tree, the attached sample C++ code fails to get compiled by clang++:

  $ clang++ -o test test.C 
  : CommandLine Error: Option 'track-memory' registered more than once!
  LLVM ERROR: inconsistency in registered CommandLine options

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run 'clang++ -o test test.C'.

Actual results:
: CommandLine Error: Option 'track-memory' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

Expected results:
Compilation completes as expected.

Additional info:
- Code was still compiled correctly by clang only a fews days ago.
- Code is being compiled successfully by c++ (GCC) 6.0.0 20160212 (Red Hat 6.0.0-0.11).
Comment 1 Joachim Frieben 2016-02-17 11:23:02 EST
To be more specific: the error is merely triggered by executing 'clang'.
Comment 2 Petr Pisar 2016-02-18 02:34:33 EST
*** Bug 1309535 has been marked as a duplicate of this bug. ***
Comment 3 Dominik 'Rathann' Mierzejewski 2016-02-23 07:51:51 EST
clang is basically unusable in rawhide at the moment.
Comment 4 Jan Včelák 2016-02-23 13:41:06 EST
I think the clang is linked incorrectly.

It looks like the problem appeared quickly after switching to single libLLVM.so. I don't get the reason for this change from the commit message.


And there is also a second commit I would blame. I don't know why would the clang required llvm-static. My initial clang package built witout it and worked for me.

Comment 5 Dave Airlie 2016-02-23 15:45:21 EST
Neither of those commits should cause it though.

The single LLVM.so is because the split set is broken, and upstream isn't interested in fixing it. They stated we shouldn't be using that configuration.

So I went to the recommended upstream configuration and rebuilt things, I'm still not sure why this happens though.

The llvm-static is just due to stupid llvm cmake scripts looking for some stuff, try building without llvm-static involved and see what falls out.
Comment 6 Jan Včelák 2016-02-23 16:05:52 EST
Dave, thank you for explanation. I'll try to find some time to take a look at this then.
Comment 7 Dave Airlie 2016-02-24 02:48:14 EST
I think I've pushed the fix to the clang repo, I can't build at the moment as koji is down.
Comment 8 Jan Včelák 2016-02-24 08:02:32 EST
*** Bug 1311489 has been marked as a duplicate of this bug. ***
Comment 9 Jan Kurik 2016-02-24 10:22:40 EST
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
Comment 10 Dave Airlie 2016-02-24 20:10:40 EST
okay I think this is fixed in clang-3.8.0-0.3.fc24

reopen if not.
Comment 11 Dominik 'Rathann' Mierzejewski 2016-04-06 05:32:53 EDT
This is still an issue on s390(x), but it seems they haven't updated clang yet (3.7.1-4.fc24 gets installed in the buildroot).
Comment 12 Orion Poplawski 2017-02-09 11:40:22 EST
I'm trying to get a working clang3.7 package built (see bug #1420512) but am running into this issue as well.  I applied some changes from the clang-3.8.0-0.3 package but that did not appear to be sufficient.  Was it something in 3.8.0 that fixed it?
Comment 13 Orion Poplawski 2017-02-14 18:50:16 EST
Nevermind, I sorted it out.  Wrong version of shared libraries being loaded.

Note You need to log in before you can comment on or make changes to this bug.