Opened 9 years ago
Closed 3 years ago
#50945 closed defect (fixed)
inkscape @0.91: fatal error: 'tr1/functional' file not found
Reported by: | danielta | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | p-bro, Benusiglio, cooljeanius (Eric Gallager) | |
Port: | inkscape |
Description
Trying to install inkscape I get:
:info:build In file included from selection-chemistry.cpp:105: :info:build In file included from ./ui/tool/multi-path-manipulator.h:16: :info:build ./ui/tool/node.h:27:10: fatal error: 'tr1/functional' file not found :info:build #include <tr1/functional>
I've seen this issu addressed in this for a previous OSX version, https://bugs.launchpad.net/inkscape/+bug/1244295
any idea?
Attachments (2)
Change History (12)
comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to devans@… |
---|
comment:2 Changed 9 years ago by dbevans (David B. Evans)
Status: | new → assigned |
---|
comment:3 follow-up: 4 Changed 9 years ago by dbevans (David B. Evans)
It looks like your compiler is configured incorrectly, that is, something is overriding the ports default compiler settings. Your build uses /usr/bin/c++ but should be using /usr/bin/clang++ and the expected flags -std=c++11 -stdlib=libc++ appear to be missing.
I can't tell how this is happening because your log is not from a clean build and does not show what happened during configure. Have you made any customizations of the port or the configure/build environment variables that might be causing this problem?
Please execute the following commands and attach the resulting log which should show the configuration phase as well as the build phase up to and including the build failure.
sudo port clean inkscape sudo port install inkscape
comment:4 Changed 9 years ago by danielta
Thanks for your prompt reply. in my machine /usr/bin/c++ is a symbolic link to /usr/bin/clang++ (Apple LLVM version 7.3.0 (clang-703.0.29))
I have not modified the configuration files. Please find attached the main.log with the clean install as required.
looking forward to solve
Replying to devans@…:
It looks like your compiler is configured incorrectly, that is, something is overriding the ports default compiler settings. Your build uses /usr/bin/c++ but should be using /usr/bin/clang++ and the expected flags -std=c++11 -stdlib=libc++ appear to be missing.
I can't tell how this is happening because your log is not from a clean build and does not show what happened during configure. Have you made any customizations of the port or the configure/build environment variables that might be causing this problem?
Please execute the following commands and attach the resulting log which should show the configuration phase as well as the build phase up to and including the build failure.
sudo port clean inkscape sudo port install inkscape
Changed 9 years ago by danielta
Attachment: | clean_main.log added |
---|
comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
The second line of the log is:
:warn:main Xcode does not appear to be installed; most ports will likely fail to build.
Please install Xcode.
comment:7 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | Benusiglio added |
---|---|
Summary: | Inkscape fail compiling OSX 10.11.4 → inkscape @0.91: fatal error: 'tr1/functional' file not found |
Has duplicate #53364.
Does this problem still occur with the latest version, inkscape 0.92.2?
comment:8 Changed 7 years ago by danielta
I have tried to test but the dependency gtkspell2 returns this error:
gtkdoc-mktmpl: command not found
which sounds similar to: https://trac.macports.org/ticket/54755
how can I overcome this?
comment:9 Changed 3 years ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
comment:10 Changed 3 years ago by mascguy (Christopher Nielsen)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Since this port has now been updated to 1.1.2, please let us know if this is still an issue.
If so, we'll reopen.
Please attach the main.log file.