-
Notifications
You must be signed in to change notification settings - Fork 12
OSX Compatibility #4
Comments
Any progress on this ? I've just been bitten by the same issue. |
Not that I know of, I'll ping people involved. |
The plan is to replace inotify by a portable library, but the work hasn't started yet. |
Would be nice to at least not fail on inotify when not running in a polling mode. Also there are some "scary" warnings which would be nice to not print at the start of the day:
|
A fully portable inotify is kind of tricky -- being able to disable the polling functionality entirely and do a one-shot build would be very useful. |
I managed to get past this first error message but I then get a new one:
|
Set the environment variable JENGA_USE_OCAML_DIGEST and try again. We should fix jenga so that it doesn't have a hard-coded dependency on /usr/bin/md5sum (which of course is called "md5" on the Mac). |
Also, it might be helpful to run with -verbose. |
seems to work now, thanks!
|
marvellous. |
awesome! On 11 Jun 2014, at 16:54, Mark Shinwell notifications@github.com wrote:
|
The "scary" warnings:
are because jenga attempts to determine the number of CPUs in order to choose a sensible default for the -j and -f flags. It fails, so you get j-1, f=1 (as it shows you). If you want parallel builds, you will have to set -j on the command line. (#cpus-1) is a reasonable choice - but please experiment. Sadly this wont make the scary message go away. The proper fix is for jenga to use an architecture independent way of determining the CPU count. |
We're fixing Core to use the sysconf method to determine the number of cores, which will fix the /proc/cpuinfo problems (and make it know how many cores there are on a Mac). |
Need to guard sysconf around Linux|Darwin, as BSDs use sysctl to retrieve this information. On 12 Jun 2014, at 10:47, Mark Shinwell notifications@github.com wrote:
|
Really? I thought sysconf was a POSIX standard function... |
sysconf is, but _SC_NPROCESSORS_ONLN isnt mandated by POSIX yet [1]. I've just checked on modern OpenBSD and it does have it now, so it may be ok to depend on. Still good to guard it behind a #ifdef and default to one if not present. [1] http://austingroupbugs.net/view.php?id=339 -a On 16 Jun 2014, at 09:10, Mark Shinwell notifications@github.com wrote:
|
Hey everyone, I'm trying to use jenga built from master on OS X 10.11 beta and am getting this error when running the command
I initially thought it was related to flock which apparently shouldn't be used on OS X (and lockf is preferred). I tried removing the |
@bsansouci, I noticed this as well the other day when trying jenga on my laptop. IIRC replacing |
hey @diml thanks for that! I was building core wrong and it wasn't picking up my changes. This worked but I don't think we need to use both flock and lockf seeing how flock is supposed to be strictly better than lockf. |
No problem. We should include the proposed fix in a minor release of core, and we'll look for a better one for future releases; we'll need to add more |
Running jenga on OSX against of the examples gives:
Seems like this is because inotify is absent from OSX.
The text was updated successfully, but these errors were encountered: