-
Notifications
You must be signed in to change notification settings - Fork 233
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
fix openbsd build #659
fix openbsd build #659
Conversation
Hi. Thanks for the patch. In the light of #658, maybe it is better to find a more robust way to generate the socket path. |
Ok, thanks. Since I am working on OpenBSD I'll be glad to take care of the testing if needed. |
xguerin: can you try to rebase on current master? If it works, I will happily merge your PR. Thanks. |
Done. However, recent versions of merlin 3.0 are behaving strangely on
I have not taken an in-depth look at what may be the source of the problem ( |
I was able to run your patched version on OpenBSD (6.1) without problem, so the problem must come from a difference in your setup. I tried with vim. |
How do you call It seems that It looks like the culprit may be However, I don't really see the point of calling |
I see. My .vimrc for merlin development might workaround the issue. The purpose of |
What about checking EDIT I apologize for being so dense, but although I get the reason why you want to use if (realpath(argv0, merlin_path) == NULL) From the OpenBSD MAN: All but the last component of pathname must exist when realpath() is called. Which differs apparently from the Linux version where all components must exist, period. However, since My understanding is that you want to check whether or not a the binary was called using a path so you can either use that path (if it exists) to run If my interpretation is correct, I gave it a shot here: #667. |
No description provided.