Hi developers!
I’m trying to get the new Portfile ncplot to UseTheRightCompiler. It uses a
primitive Makefile but not a configure file. So I added the makefile 1.0
portgroup. However, I get a build error when I do. Can anyone help?
Error is:
:info:build In file included from init.c:22:
:info:
On Jul 23, 2020, at 10:18, Frank Schima wrote:
> I’m trying to get the new Portfile ncplot to UseTheRightCompiler. It uses a
> primitive Makefile but not a configure file. So I added the makefile 1.0
> portgroup. However, I get a build error when I do. Can anyone help?
>
> Error is:
>
> :in
Hi Ryan,
> On Jul 23, 2020, at 9:52 AM, Ryan Schmidt wrote:
>
> On Jul 23, 2020, at 10:18, Frank Schima wrote:
>
>> I’m trying to get the new Portfile ncplot to UseTheRightCompiler. It uses a
>> primitive Makefile but not a configure file. So I added the makefile 1.0
>> portgroup. However, I
> On Jul 23, 2020, at 11:27, Frank Schima wrote:
>
> Hi Ryan,
>
>> On Jul 23, 2020, at 9:52 AM, Ryan Schmidt wrote:
>>
>> On Jul 23, 2020, at 10:18, Frank Schima wrote:
>>
>>> I’m trying to get the new Portfile ncplot to UseTheRightCompiler. It uses a
>>> primitive Makefile but not a conf
> Mojave 10.14 and later doesn't provide /usr/include anymore. System headers
> like are only in the SDK now. Note the -isystem flag with the
> path to the SDK isn't in that compile line. MacPorts put that flag into
> CFLAGS, CXXFLAGS, CPPFLAGS, and a comparable one into LDFLAGS for you, so
>
On Jul 23, 2020, at 11:53, Christopher Jones wrote:
>> Mojave 10.14 and later doesn't provide /usr/include anymore. System headers
>> like are only in the SDK now. Note the -isystem flag with the
>> path to the SDK isn't in that compile line. MacPorts put that flag into
>> CFLAGS, CXXFLAGS,
> Hi developers!
>
>
> I’m trying to get the new Portfile ncplot to UseTheRightCompiler. It uses a
> primitive Makefile but not a configure file. So I added the makefile 1.0
> portgroup. However, I get a build error when I do. Can anyone help?
>
> Error is:
>
> :info:build In file included fr
> You have to use clang++ if you are calling in c++ includes.
>
> Then it will work.
Having read over the other comments, and in case that wan’t clear — if you use
/usr/bin/clang++ your build will automatically find the c++ includes, and you
don’t need to do any of those suggestions with -isysr