-
-
Notifications
You must be signed in to change notification settings - Fork 663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[haxe 4.3.4] build errors #11878
Comments
What exactly did you put in the LDFLAGS/CPPFLAGS? On intel macs, homebrew installs to You may need to modify the dune files in a similar way to: #11195 |
On my machine, |
I modified the dune configuration files
Now the build script can find the libraries.
|
Do you have neko installed on your system? If so, how did you install it? |
Well, I fixed the problem by setting the NEKOPATH variable ( |
It may be best to keep this issue open until a better solution is found, as I suspect building from |
Another way to solve this without modifying any build files is to set the following environment variables: export C_INCLUDE_PATH=$(brew --prefix zlib)/include:$(brew --prefix)/include
export LIBRARY_PATH=$(brew --prefix zlib)/lib:$(brew --prefix)/lib Zlib is "keg-only" (not linked in the global brew prefix) to avoid interfering with the system version, which is why the zlib paths have to be added explicitly. If you are compiling a 4.3.x build, that doesn't support mbedtls 3 yet so you have to also add I was also considering whether this should be handled by |
Perhaps you meant |
Is there an issue with pcre2 still? Both
|
No, I don't have any problems. However, since this issue mentions |
I'm trying to compile Haxe 4.3.4 on a Mac M2 running Sequoia 15.1.1 and OCaml 5.2.1.
I've encountered some issues along the way, but I've managed to resolve most of them (#11787 #10679 #11874).
Now, I'm facing the following errors:
I've installed both
pcre2
andmbedtls@2
through Homebrew.Here are the installation details:
I've also tried setting the LDFLAGS and CPPFLAGS variables to the library locations, but it seems the build script does not use them.
The text was updated successfully, but these errors were encountered: