On Jul 24, 2020, at 13:47, Frank Schima wrote:
> I tried setting CC like so:
>
> build.args CC="${configure.cpp} [get_canonical_archflags cc]"
>
> But it still does not work. Here is the resulting compiler used:
>
> /usr/bin/cpp -arch x86_64 -Wall -g -O2 -I/opt/X11/include -DPNG -DP
> On Jul 24, 2020, at 1:17 PM, Ken Cunningham
> wrote:
>
>> build.args CC="${configure.cpp} [get_canonical_archflags cc]"
>
> Try this perhaps:
>
> build.args CC="${configure.cxx} [get_canonical_archflags cxx]"
>
> There are other methods some might prefer besides this. BTW, the
You should be setting CXX, not CC, to define the c++ compiler to use…
Chris
> On 24 Jul 2020, at 7:47 pm, Frank Schima wrote:
>
> Hi Ken,
>
>> On Jul 23, 2020, at 10:38 PM, Ken Cunningham
>> mailto:ken.cunningham.web...@gmail.com>>
>> wrote:
>>
>>> You have to use clang++ if you are callin
> build.args CC="${configure.cpp} [get_canonical_archflags cc]"
Try this perhaps:
build.args CC="${configure.cxx} [get_canonical_archflags cxx]"
There are other methods some might prefer besides this. BTW, the software has
this issue because the author threw a c++ include file into a
Hi Ken,
> On Jul 23, 2020, at 10:38 PM, Ken Cunningham
> wrote:
>
>> 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 t
> 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
> 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
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,
> 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: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
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 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 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:
13 matches
Mail list logo
