Building on macOS: Ran into trouble with iconv
#225
Replies: 6 comments 1 reply
-
In fairness, you didn't :). The official instructions for building on macOS are still somewhat... lacking. Might be worth checking against the Cirrus build script (which does actually use |
Beta Was this translation helpful? Give feedback.
-
Thanks for the lead. I have Xcode 15 installed, and the Cirrus script seems to reference Xcode 14. This seems like a salient difference, though I don't have a particular clue how to proceed. (This isn't my usual area of work. I program on a Mac, but I don't exactly do Mac programming.) |
Beta Was this translation helpful? Give feedback.
-
@danfuzz One thing I'd take a look at is the requirements of
Which would mean having:
Hopefully with those installed you should be good to go |
Beta Was this translation helpful? Give feedback.
-
Unclear if this is actually the problem, but I did find https://stackoverflow.com/questions/57734434/libiconv-or-iconv-undefined-symbol-on-mac-osx, which describes a similar situation. The accepted-answer looks like it might be spot-on. |
Beta Was this translation helpful? Give feedback.
-
Resolved! (I think) The SO link (above) helped, but it turned out that a later answer was key. $ brew install node@16
$ brew install corepack
$ brew install libiconv
$ export LDFLAGS="-L/opt/homebrew/opt/node@16/lib -L/opt/homebrew/opt/libiconv/lib"
$ export CPPFLAGS="-I/opt/homebrew/opt/node@16/include -I/opt/homebrew/opt/libiconv/include"
$ PATH="/opt/homebrew/opt/node@16/bin:$PATH"
$ corepack enable
$ cd <pulsar source directory>
$ git submodule init && git submodule update
[... and all subsequent steps as listed in the build doc ...] |
Beta Was this translation helpful? Give feedback.
-
A rather late update, but this issue should finally be more neatly resolved "out of the box" (no |
Beta Was this translation helpful? Give feedback.
-
I'm trying to get a Pulsar build up and running on my macOS laptop, and I've run into a problem which I'm not sure how to address. In particular, I don't know what specifically to blame for the following errors that were produced when I did
yarn install
:Near as I can tell, I am performing the build in an environment wherein the expected version of Node is installed. That said, I strayed from the official Pulsar build instructions and used explicit
PATH
manipulation to set it up instead of usingnvm
(which I don't have installed; I just use Homebrew and don't want to mess with my usual setup for this foray):While I believe what I did to set up my environment is kosher, I'm not 100% sure. I'd be most appreciative of any guidance. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions