K Jelesnianski via llvm-dev
2020-Jul-13 02:22 UTC
[llvm-dev] LLVM source compilation Error: CommandLine Error: Option 'mc-relax-all' registered more than once!
Thanks for your quick reply. I have also tried disabling build shared libs, specifying via "-DBUILD_SHARED_LIBS=OFF" in my cmake config line However I am getting the same exact error with this flag specified as well. Just an idea, would removing all llvm/clang instances/libs on my machine work? Do you know what the default location is of these shared/static llvm libraries that are conflicting? I'm not exactly sure how to do this via command line on linux though. I definitely agree this is related to linkage error as you say. I'm just not sure what I have to remove to get this server to go back to a "clean slate" state such that I can build llvm-project. That is information I have been looking for, but can't seem to find and this error doesn't seem to be well documented. I have already tried the following, but it didn't help either $ sudo su $ dnf remove llvm $ dnf remove clang and then performing $ sudo dnf install llvm $ sudo dnf install clang To give more context, I can do a clean install of vanilla llvm-project on other servers I have access to, but can't currently afford to move my code base to these other servers.
K Jelesnianski via llvm-dev
2020-Jul-13 02:43 UTC
[llvm-dev] LLVM source compilation Error: CommandLine Error: Option 'mc-relax-all' registered more than once!
I found a work around. I did some more poking around my system and found where the default install location of all libLLVM* libraries and libclang* libraries were installed. Specifically $ /usr/local/lib I was hesitant but when I deleted all libclang* and libLLVM* files. I was able to get past this error. Thanks again. On Sun, Jul 12, 2020 at 10:22 PM K Jelesnianski <kjski at vt.edu> wrote:> > Thanks for your quick reply. I have also tried disabling build shared > libs, specifying via > "-DBUILD_SHARED_LIBS=OFF" in my cmake config line > However I am getting the same exact error with this flag specified as well. > > Just an idea, would removing all llvm/clang instances/libs on my > machine work? Do you know what the default location is of these > shared/static llvm libraries that are conflicting? > > I'm not exactly sure how to do this via command line on linux though. > I definitely agree this is related to linkage error as you say. I'm > just not sure what I have to remove to get this server to go back to a > "clean slate" state such that I can build llvm-project. That is > information I have been looking for, but can't seem to find and this > error doesn't seem to be well documented. > I have already tried the following, but it didn't help either > $ sudo su > $ dnf remove llvm > $ dnf remove clang > > and then performing > $ sudo dnf install llvm > $ sudo dnf install clang > > To give more context, I can do a clean install of vanilla llvm-project > on other servers I have access to, but can't currently afford to move > my code base to these other servers.
Stephen Neuendorffer via llvm-dev
2020-Jul-13 02:58 UTC
[llvm-dev] LLVM source compilation Error: CommandLine Error: Option 'mc-relax-all' registered more than once!
Aha! Good guess. It definitely looks like it is confused with the clang installed in your system somehow. Steve On Sun, Jul 12, 2020, 7:44 PM K Jelesnianski <kjski at vt.edu> wrote:> I found a work around. I did some more poking around my system and > found where the default install location of all > libLLVM* libraries and > libclang* libraries were installed. Specifically > $ /usr/local/lib > I was hesitant but when I deleted all libclang* and libLLVM* files. I > was able to get past this error. > > Thanks again. > > On Sun, Jul 12, 2020 at 10:22 PM K Jelesnianski <kjski at vt.edu> wrote: > > > > Thanks for your quick reply. I have also tried disabling build shared > > libs, specifying via > > "-DBUILD_SHARED_LIBS=OFF" in my cmake config line > > However I am getting the same exact error with this flag specified as > well. > > > > Just an idea, would removing all llvm/clang instances/libs on my > > machine work? Do you know what the default location is of these > > shared/static llvm libraries that are conflicting? > > > > I'm not exactly sure how to do this via command line on linux though. > > I definitely agree this is related to linkage error as you say. I'm > > just not sure what I have to remove to get this server to go back to a > > "clean slate" state such that I can build llvm-project. That is > > information I have been looking for, but can't seem to find and this > > error doesn't seem to be well documented. > > I have already tried the following, but it didn't help either > > $ sudo su > > $ dnf remove llvm > > $ dnf remove clang > > > > and then performing > > $ sudo dnf install llvm > > $ sudo dnf install clang > > > > To give more context, I can do a clean install of vanilla llvm-project > > on other servers I have access to, but can't currently afford to move > > my code base to these other servers. >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200712/debd1e33/attachment.html>