After further investigation, the regression started in Gradle 1.12, and happens as soon as we use one samba mount point that points to a Windows OS: the stat command returns an Inode that's bigger than 32bit, hence the error 75 (Value too large for defined data type).
(please bear with me on the following as I have VERY little experience with g++ compiler)

The fix is to us the compiler option -D_FILE_OFFSET_BITS=64 so that the stat struct handles 64bit for the Inode value.
(see http://www.linuxquestions.org/questions/programming-9/problem-with-stat-on-cifs-852983/#post4208525)

This effectively fixes the bug for me, but I don't know if it could have negative implications. If it doesn't, I suppose the same option should be used for OSX, but unfortunately I have no way of testing it.
I created a pull request: https://github.com/adammurdoch/native-platform/pull/7

Out of curiosity, was there a change in your build platform between version 0.7 and 0.8 of native-platform that could explain the regression? there doesn't seem to be anything really different between the two versions regarding the call to stat?

Edit: I should probably mention that all tests were done on 32bit OSes (Ubuntu and Debian)

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.