Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packaging (conda): CommandLine Error: Option 'disable-symbolication' registered more than once! #440

Closed
SylvainCorlay opened this issue Sep 20, 2021 · 6 comments · Fixed by root-project/root#11703

Comments

@SylvainCorlay
Copy link
Contributor

As I am working on getting cling 0.9 packaged for conda-forge.

I managed to successfully build cling, however, I am seeing the following failure at run time:

CommandLine Error: Option 'disable-symbolication' registered more than once!
@Axel-Naumann
Copy link
Member

That's two sets of LLVM libraries getting symbol-confused. For ROOT we hide all of LLVM's symbols for that exact reason. What libraries are loaded into your cling, what's the OS etc?

@Axel-Naumann Axel-Naumann self-assigned this Nov 11, 2021
@Axel-Naumann
Copy link
Member

Is this still an issue, @SylvainCorlay ?

@SylvainCorlay
Copy link
Contributor Author

Yes, I have not been able to put cycles into this recently unfortuntely.

@Axel-Naumann
Copy link
Member

OK will leave it open then until you come back to us (or until it gets self-healed with a subsequent llvm update)

@SylvainCorlay
Copy link
Contributor Author

@serge-sans-paille was able to figure it out, and patched the conda recipe for cling 0.9 in the following way:

conda-forge/cling-feedstock@f42b723

@SylvainCorlay
Copy link
Contributor Author

@Axel-Naumann let me know if this solution is useful to you.

serge-sans-paille added a commit to serge-sans-paille/cling that referenced this issue Nov 3, 2022
LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project#440
vgvassilev pushed a commit to vgvassilev/root that referenced this issue Nov 14, 2022
LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440
vgvassilev added a commit to root-project/root that referenced this issue Jan 20, 2023
#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440
FonsRademakers pushed a commit that referenced this issue Jan 20, 2023
…t (#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix #440
Axel-Naumann pushed a commit to Axel-Naumann/root that referenced this issue Mar 17, 2023
root-project#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440

(cherry picked from commit 286d96b)
Axel-Naumann pushed a commit to Axel-Naumann/root that referenced this issue Mar 20, 2023
root-project#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440

(cherry picked from commit 286d96b)
Axel-Naumann pushed a commit to root-project/root that referenced this issue Mar 20, 2023
#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440

(cherry picked from commit 286d96b)
omazapa pushed a commit to omazapa/root that referenced this issue Apr 13, 2023
root-project#11703)

Do not register LLVMSupport as a library when it should be a component

LLVM component must be registered as LLVM_LINK_COMPONENTS to be
compatible with LLVM Dylib. Otherwise they are loaded twice in the final
binary, once through LLVM Dylmib and once through individual component,
and this results in some options being registered twice.

Fix root-project/cling#440
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment