Opened 5 years ago
Last modified 6 months ago
#59843 assigned defect
ds9 @8.1_1 build failure
Reported by: | manulcaux | Owned by: | lpsinger (Leo Singer) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | Cc: | ||
Port: | ds9 |
Description
On a MacBook Pro running MacOS 10.14.6 and Xcode 11.3, I cannot install ds9. It was installed, I just tried to upgrade all my outdated ports when this error appeared.
Attachments (1)
Change History (5)
Changed 5 years ago by manulcaux
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Milestone: | MacPorts Future |
---|---|
Owner: | set to lpsinger |
Status: | new → assigned |
Summary: | ds9 does not install → ds9 @8.1_1 build failure |
comment:2 Changed 5 years ago by manulcaux
Hi, I tried again today to upgrade ds9, failed with the same error... Will I have some news ?
comment:3 follow-up: 4 Changed 5 years ago by lpsinger (Leo Singer)
I think that the problem may be here, in the first few lines of the log:
:warn:main The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly. 8 :warn:main You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
Are you certain that you have run xcode-select --install
?
comment:4 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to lpsinger:
I think that the problem may be here, in the first few lines of the log:
:warn:main The macOS 10.14 SDK does not appear to be installed. Ports may not build correctly. 8 :warn:main You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
I would ignore that. More relevant to me seems to be the following:
In file included from iistcl.C:7: In file included from /opt/local/include/stdlib.h:36: /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:101:9: error: no member named 'div_t' in the global namespace using ::div_t; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:102:9: error: no member named 'ldiv_t' in the global namespace using ::ldiv_t; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:104:9: error: no member named 'lldiv_t' in the global namespace using ::lldiv_t; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:106:9: error: no member named 'atof' in the global namespace using ::atof; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:107:9: error: no member named 'atoi' in the global namespace using ::atoi; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:108:9: error: no member named 'atol' in the global namespace using ::atol; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:110:9: error: no member named 'atoll' in the global namespace using ::atoll; ~~^ /Library/Developer/CommandLineTools/usr/include/c++/v1/cstdlib:112:9: error: no member named 'strtod' in the global namespace; did you mean 'strtok'? using ::strtod; ~~^ /usr/include/string.h:90:7: note: 'strtok' declared here char *strtok(char *__str, const char *__sep); ^
In other words, some port has installed /opt/local/include/stdlib.h, it is being found instead of the normal stdlib.h, and it is not compatible with the normal stdlib.h and is causing errors. Remove whatever port installed that. Searching the ports web site today, I can't find any port that installs that file, so maybe it has already been solved. If not, you can use port provides /opt/local/include/stdlib.h
to find out which port provided that file, then sudo port uninstall
it, and report it to us so we can fix that port to not do that.
main.log file just after the crash of ds9 install