$340 in bounties won
Total Bounty: $20
While building 0.175 on kFreeBSD, error encountered.
Is a1f9b62dd0a491d6b26291837d43181c0e9e66fa enough to fix this?
Sorry, I didn't realise I commented on the actual commit, not issue. No, this commit does not fix it.
Coderbounty posted: http://coderbounty.com/issue/68
What version of kFreeBSD?
Following up. I was able to build mame HEAD on jessie-kFreeBSD with a number small build patches, mostly to `uv`.
With the fixes from #1093, and using system libuv, yes, the build succeeds, as can be seen here: https://buildd.debian.org/status/fetch.php?pkg=mame&arch=kfreebsd-amd64&ver=0.176-2&stamp=1469694187
This bug should have been closed a week ago.
These are Debian's libuv portability patches: https://sources.debian.net/src/libuv/0.10.36-3/debian/patches/ . It might be a good idea to merge a good part of these into 3rdparty.
so who wins the $20? :smiley: (man, that was totally random...)
@jmallach @mmicko UV upstream PR for GNU/kFreeBSD support https://github.com/libuv/libuv/pull/959
TBH, if anyone deserves these $20, it's @stevenc99. But how on earth did these $20 appear out of nowhere?