Opened 10 years ago
Closed 9 years ago
#45400 closed defect (fixed)
root6: error: thread-local storage is unsupported for the current target
Reported by: | watsodw | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cjones051073 (Chris Jones), mojca (Mojca Miklavec), cooljeanius (Eric Gallager) | |
Port: | root6 |
Description (last modified by mojca (Mojca Miklavec))
See log.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_root6/root6/work/root-f460f42728305617c4978ced32bd030b1b4279e0/core/unix/src/TUnixSystem.cxx:401:4: error: thread-local storage is unsupported for the current target :info:build thread_local TString exepath; :info:build ^
Attachments (1)
Change History (11)
Changed 10 years ago by watsodw
comment:1 Changed 10 years ago by cjones051073 (Chris Jones)
comment:2 Changed 10 years ago by cjones051073 (Chris Jones)
Is your Xcode and command lines tools up to date ?
I have
MacBookPro ~/Downloads > /usr/bin/clang -v Apple LLVM version 6.0 (clang-600.0.51) (based on LLVM 3.5svn) Target: x86_64-apple-darwin13.4.0 Thread model: posix
whereas your log says
:info:configure -- The C compiler identification is AppleClang 5.0.0.5000279 :info:configure -- The CXX compiler identification is AppleClang 5.0.0.5000279
Please make sure you are using the latest versions compatible with OSX10.9, and then try again.
Chris
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | root6 fails to uggrade → root6: error: thread-local storage is unsupported for the current target |
---|
comment:4 Changed 10 years ago by cooljeanius (Eric Gallager)
I think the issue of thread-local storage came up in #44062 previously, although I would have thought that the version of clang being used here would work based on that...
comment:6 Changed 10 years ago by cjones051073 (Chris Jones)
Hi,
The error message here is the same as in the OSX 10.6 log file in #45265, that ultimately lead to that OS no longer being supported by the root6 port.
I still suspect the OP's Xcode and/or command line tools are not the latest, which is required to support root6. Updating is I think the solution. Failing that, if they are not willing, then try with the +clang34 variant, that then forces the use of macPorts Clang 3.4 compiler. This is the compiler used on OSX 10.7 and 10.8, for the very reason that the default compilers there are also not up to date enough to support compiling root6.
Chris
comment:7 Changed 10 years ago by watsodw
I did an uninstall, upgraded my Xcode to 5.1.1 and tried again, and doing one or both of those allowed it to install cleanly. Thanks guys.
comment:8 Changed 10 years ago by cjones051073 (Chris Jones)
Thanks for the feedback. Useful to know root6 did not support the older Xcode...
comment:9 Changed 9 years ago by bpnuke@…
I have been trying to compile against the root libraries provided through macports and keep running into a similar error posted in this following URL.
https://root.cern.ch/phpBB3/viewtopic.php?t=19551&p=83737
The root developers say they've fixed the problem and that it is now compatible with OS X 10.10.3 Xcode 6.3.2 and this is correct. If I re-compile the root v6-04-00 natively on my machine, I don't have an issue compiling against the headers. I was wondering what version of Xcode/clang this current port was compiled with and if it could be recompiled to bring it up-to-date. That is if it'll actually fix the problem. May just be a problem on my end.
comment:10 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Version: | 2.3.1 |
This report was about ROOT 6.02.00. Based on the reply and the link on the forum I guess this has been solved with new version of ROOT? (We are at version 6.06.00 now.)
In case this is still a problem, please reopen the ticket or open a new one.
What variants are you using (not so easy to decipher from the log...).
Can you try an uninstall followed by clean install, rather than an upgrade ?
Chris