> On 23 Nov 2019, at 1:56 pm, Steven Smith <[email protected]> wrote: > > Per https://guide.macports.org/#reference.phases.installation.list-modifiers > <https://guide.macports.org/#reference.phases.installation.list-modifiers>, > I’ll try starting with a blanket -delete of everything, try to get to the > basic working make, and divide-and-conquer to isolate the issue. Maybe this? > >> configure.cflags-delete >> configure.ldflags-delete >> … > > > Is there an equivalent build.cflags, build.ldflags, etc.? > > There is not configure step necessary for this repo. Are these MacPorts > configure flags used in the build stage?
you can get a detailed summary of what is set for each phase, by running with > port -d ….. Chris > > Here’s the current not-working Portfile: > > https://github.com/macports/macports-ports/blob/4a9cd2d6b34e6d48e22bfb608529e900f49f8dcb/devel/jsonnet/Portfile > > <https://github.com/macports/macports-ports/blob/4a9cd2d6b34e6d48e22bfb608529e900f49f8dcb/devel/jsonnet/Portfile> > > >> On Nov 23, 2019, at 8:25 AM, Chris Jones <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> >>> On 23 Nov 2019, at 12:57 pm, Steven Smith <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>>> >>>> You need to try and isolate the one causing the issue, if you believe it >>>> is something MacPorts is appending to the env, and then address that >>>> specifically. >>> >>> That’s what I’m asking for help to do. >>> >>> How are these flags and environment variables set within a Portfile? >>> >>> I don’t know enough about the MacPorts build design or clang options enough >>> to go through all the combinatoric flag settings, or to divide-and-conquer >>> the problem. >>> >>> Here are the flags set by Google’s upstream repo, >>> <https://github.com/google/jsonnet/blob/master/Makefile >>> <https://github.com/google/jsonnet/blob/master/Makefile>>: >>>> CXXFLAGS ?= -g $(OPT) -Wall -Wextra -Woverloaded-virtual -pedantic >>>> -std=c++0x -fPIC >>>> CXXFLAGS += -Iinclude -Ithird_party/md5 -Ithird_party/json >>>> CFLAGS ?= -g $(OPT) -Wall -Wextra -pedantic -std=c99 -fPIC >>>> CFLAGS += -Iinclude >>>> MAKEDEPENDFLAGS += -Iinclude -Ithird_party/md5 -Ithird_party/json >>>> EMCXXFLAGS = $(CXXFLAGS) -g0 -Os --memory-init-file 0 -s >>>> DISABLE_EXCEPTION_CATCHING=0 -s OUTLINING_LIMIT=10000 -s >>>> RESERVED_FUNCTION_POINTERS=20 -s ASSERTIONS=1 -s ALLOW_MEMORY_GROWTH=1 >>>> EMCFLAGS = $(CFLAGS) --memory-init-file 0 -s DISABLE_EXCEPTION_CATCHING=0 >>>> -s ASSERTIONS=1 -s ALLOW_MEMORY_GROWTH=1 >>>> LDFLAGS ?= >>> >>> >>> How are these variables and flags unset/reset within a Portfile? >> >> See >> >> https://guide.macports.org/ <https://guide.macports.org/> >> >> There is a section in there explaining how CFLAGS etc. are set. >>> >
smime.p7s
Description: S/MIME cryptographic signature
