[MacPorts] #53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++
MacPorts
noreply at macports.org
Mon Dec 12 12:56:05 CET 2016
#53044: octave @4.2.0_1: error: 'cstdint' file not found with libstdc++
---------------------+---------------------------------
Reporter: mojca | Owner: MarcusCalhoun-Lopez
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: snowleopard lion
Port: octave |
---------------------+---------------------------------
Comment (by MarcusCalhoun-Lopez):
Replying to [comment:4 mojca]:
> I didn't test the new commit yet, but in my case GraphicsMagick has been
compiled with the standard/default clang compiler against `libstdc++`
rather than with gcc (against gcc's own & incompatible `libstdc++`).
>
> If the dependency indeed has to be compiled with the same compiler, you
are calling for bigger troubles by switching to `macports-gcc-6`.
Octave only silently defaults to macports-gcc-6 if
{{{${configure.cxx_stdlib} eq "libstdc++"}}}.[[BR]]
On 10.12, 10.11, and 10.10, the system clang is used.[[BR]]
On 10.9, macports-clang is used because the buildbot failure seems to
indicate the system clang doesn't work.[[BR]]
On 10.8, macports-gcc is used since C++11 is required.[[BR]]
This assumes, of course, that the user hasn't intentionally set
{{{configure.cxx_stdlib}}} to something else.
If the user specifically requests a {{{gcc*}}} variant, then the
{{{graphicsmagick}}} variant is not the default and is marked in conflict.
Won't this keep the C++ standard library consistent?[[BR]]
I am a little bit new to {{{compiler.blacklist}}} and
{{{compiler.whitelist}}}.[[BR]]
Please feel free to correct my assessment.
--
Ticket URL: <https://trac.macports.org/ticket/53044#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list