-
Notifications
You must be signed in to change notification settings - Fork 22
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
Trouble building and testing on Mac OS 14 #127
Comments
Another related issue with building on Mac that I neglected to mention in the initial description is relative paths are ineffective when supplied to the
Looking in the folder it mentions ( I think this is fixable but I'm low on implementation details at the moment and can't yet propose a fix. My current workaround is specifying the absolute path to my source tree. |
Nim v1.6.20
I'm unable to use futhark with Nim v1.6.x:
I have a workaround for this using Nim v2.x to run futhark for generating wrapper code, but I have a preference for 1.6.x since another library I'm using (
uing
) behaves more predictably at runtime when compiled with older Nim. It'd be nice if I could avoid runningchoosenim
for this step.Nim v2.x
Using Nim v2.2.0 yields better results, but unless I explicitly specify
sysPath
, it fails to findstdio.h
:Again, there's a workaround for this, but this does seem like unexpected behavior to me, and maybe it's possible for futhark to auto-detect a proper
sysPath
within awhen(macosx)
block.Test
When I build on Linux things more-or-less work without additional effort. On Mac, I'm unable to run a test binary despite adding the following to the top of my library:
SIGSEGV
(redacted)
This one gets resolved at runtime by adding
VLC_PLUGIN_PATH
to the environment. No more SIGSEGV, just a known libvlc on Mac quirk.Sorry for opening such a long-bodied issue, I just figured having this all in one place would be more useful than opening several related issues.
The text was updated successfully, but these errors were encountered: