Opened 8 years ago
Closed 8 years ago
#52142 closed defect (invalid)
root5 fails to build on Mac OSX 10.11.4
Reported by: | donal.hill@… | Owned by: | cjones051073 (Chris Jones) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ||
Port: | root5 |
Description
Hi there,
I believe that this issue has been discussed previously on another thread (#50998), but I am unsure whether it relates to my specific case.
I am attempting to run:
"sudo port install root5"
and I run into errors as descried in the attached log file. I have had no problems installing root6 on the same machine.
Any help would be great!
Cheers, Donal
Attachments (2)
Change History (12)
Changed 8 years ago by donal.hill@…
comment:1 Changed 8 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to jonesc@… |
---|
In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers root5
), if any.
comment:2 Changed 8 years ago by gnw3
Your log has:
:info:build /opt/local/bin/clang-mp-3.3 -O2 -m64 -pipe -Wshadow -W -Wall -fsigne d-char -fno-common -Iinclude -DR__HAVE_CONFIG -pthread -o core/clib/src/mmtr ace.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.mac ports.org_release_tarballs_ports_science_root5/root5/work/root-5-34-36/core/clib /src/mmtrace.c :info:build In file included from /opt/local/var/macports/build/_opt_local_var_m acports_sources_rsync.macports.org_release_tarballs_ports_science_root5/root5/wo rk/root-5-34-36/core/macosx/src/CocoaUtils.mm:12: :info:build In file included from include/CocoaUtils.h:17: :info:build In file included from /System/Library/Frameworks/Foundation.framewor k/Headers/Foundation.h:10: :info:build In file included from /System/Library/Frameworks/Foundation.framewor k/Headers/NSArray.h:5: :info:build /System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:19:21: error: expected a type :info:build - (id)copyWithZone:(nullable NSZone *)zone; :info:build ^ :info:build /System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:25:28: error: expected a type :info:build - (id)mutableCopyWithZone:(nullable NSZone *)zone;
Ticket 49440 reports a similar error due to using Xcode version
lower than 7 on El Capitan. If you are using Xcode 7, try building without the +clang33
option.
comment:3 Changed 8 years ago by cjones051073 (Chris Jones)
( hi Donal !! )
Something is fishy with your log. I don't see the configure step I would expect. Was it really from a clean build ?
Please rerun
sudo port clean root5 sudo port install root5
and post the log.
Its very strange that MacPorts clang 3.3 is being used, that should not happen, and does not for me. i.e. from my logs I see during the configure phase
Checking for C compiler ... /usr/bin/clang Checking for C++ compiler ... /usr/bin/clang++ Checking for linker (LD) ... /usr/bin/clang++
So it is using the system clang compiler as expected.
Can you please, as has already been suggested, make sure you are running the correct and up to date Xcode for OS X 10.11 *and* that you have re-installed the command line tools correctly. See
for details.
root5 builds fine for me, and also in the build-bots, so it must be something up with your setup.
Chris
comment:4 Changed 8 years ago by cjones051073 (Chris Jones)
Please supply the requested information, otherwise I will recommended resolving this as INVALID.
cheers Chris
comment:5 Changed 8 years ago by donal.hill@…
Hi Chris,
Sorry for the delay, I got sidetracked and had to resort to installing root5 from source via the ROOT webpage.
I did a clean install of Xcode and command line tools, and did a clean build as you suggested. I attach the new log file here.
I recall sniffing around clang33 some months ago in relation to another piece of software, but I'm not sure why it's getting picked up in only the root5 build. It doesn't get used in the root6 one.
Cheers, Donal
comment:6 Changed 8 years ago by cjones051073 (Chris Jones)
I suspect you must have changed some global setting to force the use of clang 3.3, I cannot think of another reason why ROOT5 is deciding to use this. I think you need to try and remember what exactly you did a few months back ...
comment:7 Changed 8 years ago by cjones051073 (Chris Jones)
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main Requested variant -x11 is not provided by port gcc5. :debug:main Requested variant +no_x11 is not provided by port gcc5. :debug:main Requested variant +quartz is not provided by port gcc5. :debug:main Requested variant +clang33 is not provided by port gcc5.
Did you by chance tweak your general configuration to force add +clang33 as a default variant in all cases in /opt/local/etc/macports/variants.conf ?
If so, then don't do this. Its a bad idea.
Chris
comment:8 Changed 8 years ago by donal.hill@…
Hi Chris,
It looks like I had the following line in my variants.conf file:
-x11 +no_x11 +quartz +clang33
which has clearly happened as a result of me fiddling a few months back. I just removed clang33 and did a clean build of root5, and it worked :)
Thanks for the help! Donal
comment:9 Changed 8 years ago by mf2k (Frank Schima)
You can also remove the useless +no_x11
variant because no port uses that anymore. See #39383.
comment:10 Changed 8 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Log file from attempted root5 build