Undefined symbols for architecture x86_64 on jsonnet submission
Steven Smith
steve.t.smith at gmail.com
Sat Nov 23 12:57:38 UTC 2019
> 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>:
> 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191123/bc2e9cc9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3898 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191123/bc2e9cc9/attachment.bin>
More information about the macports-dev
mailing list