-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
FeeBSD Support #639
Comments
If I try 20-beta, it works, so maybe it's some kind of incompatibility issue on 19-beta with FreeBSD 13 vs 14? It can't be since it worked in an empty directory.
|
Yes, it's some kind of a diffrence between FreeBSD 13 and 14, but it looks limited to a specific project. Lets try it out on FreeBSD 13.2 first (freshly installed OS)
That was flawless. Now lets do FreeBSD 14.1 (also a fresh install)
It fails. What if we try to just install
Fails in the same way. Lets try to install
It works. Now.... lets try version 6.0.0-beta.20
That worked, and now I can run
So what's going on? |
We don't test FreeBSD in the CI, so I don't know how good our support is for that platform. |
I am running into the same issue on FreeBSD 14.1. Also mystified why sometimes it builds, sometimes not. Perhaps one way to build it would be to use shared libzmq, however that currently does not work on FreeBSD due to linking issue. Perhaps #641 could help. |
Tested on
If I run
npm install zeromq
, in an empty directory It completes without any trouble:However, if I run it within the project's directory of https://github.com/benjamin-wilson/public-pool, it fails:
Even more bizarre is that is seems to all work fine on a system using:
This makes no sense to me?
The text was updated successfully, but these errors were encountered: