-
Notifications
You must be signed in to change notification settings - Fork 275
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
Comments
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? |
Is this still an issue, @SylvainCorlay ? |
Yes, I have not been able to put cycles into this recently unfortuntely. |
OK will leave it open then until you come back to us (or until it gets self-healed with a subsequent llvm update) |
@serge-sans-paille was able to figure it out, and patched the conda recipe for cling 0.9 in the following way: |
@Axel-Naumann let me know if this solution is useful to you. |
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
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
#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
…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
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)
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)
#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)
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
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:
The text was updated successfully, but these errors were encountered: