Replies: 3 comments
-
You should activaye the arm64 brew for an arm64 build, use a arm64 pypy2.7 for translation, and make sure you have not activated the x86_64 brew in that shell. |
Beta Was this translation helpful? Give feedback.
-
And make sure pkg-config returns the correct gettext |
Beta Was this translation helpful? Give feedback.
-
I managed to get it to work by unlinking the x86_64 version of |
Beta Was this translation helpful? Give feedback.
-
I am trying to build pypy from source using a brew-installed pypy following the guide on an ARM-based MacOS.
At one step of the installation process (i.e. running
pypy ../../rpython/bin/rpython --opt=jit
), I see:which is reasonable since I have both brew for arm64 and brew for x86_64 installed, and I installed
gettext
on both archs.I thought that this wouldn't be a big deal, but trying to run the
pypy-c
executable fails with missing gettext symbols:My question is, how do I specify the
LDFLAGS
(or whatever env variables pypy installer is looking at) so it finds the right gettext library? I tried settingLDFLAGS="-L/opt/homebrew/Cellar/gettext/<version>/lib ${LDFLAGS}"
, but that didn't work.For reference, on ARM-based MacOS, brew installs everything under
/opt/homebrew
instead of/usr/local
.Beta Was this translation helpful? Give feedback.
All reactions