[MacPorts] #56878: openscad-devel @2018.04-1: error: use of undeclared identifier 'nullptr'
MacPorts
noreply at macports.org
Sat Jul 28 06:17:57 UTC 2018
#56878: openscad-devel @2018.04-1: error: use of undeclared identifier 'nullptr'
---------------------+----------------------
Reporter: kencu | Owner: dstrubbe
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: |
---------------------+----------------------
Description changed by kencu:
Old description:
> On darwin11, build fails with above error.
>
> adding
> {{{
> PortGroup cxx11 1.1
> }}}
> didn't fix it. Thereafter adding both these:
> {{{
> configure.cxxflags-append -std=c++11
> configure.objcxxflags-append -std=c++11
> }}}
> didn't fix it either.
>
> qt4 is a bit picky/tricky about these things. I may need to edit the
> build file directly and add `-std=c++11` to the QMAKE OJCXX flags, unless
> there is an easier way.
>
> It seems (in the log) that this build specifically disables `c++11`
> earlier in the build configuration due to `libstdc++` (I guess it doesn't
> see `libc++`, and/or doesn't know what `macports-libstdc++` might be).
>
> This built fine on 10.6.8 configured to libc++, amongst other systems,
> earlier this year. I have a feeling this may be another example of the
> type of fixes we will no longer have to do once we default to `libc++` on
> all systems.
New description:
On darwin11, build fails with above error.
adding
{{{
PortGroup cxx11 1.1
}}}
didn't fix it. Thereafter adding both these:
{{{
configure.cxxflags-append -std=c++11
configure.objcxxflags-append -std=c++11
}}}
didn't fix it either.
qt4 is a bit picky/tricky about these things. I may need to edit the build
file directly and add `-std=c++11` to the QMAKE OBJCXX flags, unless there
is an easier way.
It seems (in the log) that this build specifically disables `c++11`
earlier in the build configuration due to `libstdc++` (I guess it doesn't
see `libc++`, and/or doesn't know what `macports-libstdc++` might be).
This built fine on 10.6.8 configured to libc++, amongst other systems,
earlier this year. I have a feeling this may be another example of the
type of fixes we will no longer have to do once we default to `libc++` on
all systems.
--
--
Ticket URL: <https://trac.macports.org/ticket/56878#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list