Changes made to hack a build on a win10 machine.

[durian888]

As requested by Peter Hawkins [email protected] in communication with [email protected] aka durian888

Pull request for hacks performed to make jaxlib on a win10 machine
summary of changes

djb_build_info.txt gives some details of what hacks were performed and why.
used_dot_bazelrc is a copy of the .bazelrc file that was used for the build.
Note the pulled in tensorflow code had to be hacked to make the build go through - and so are not in the repo proper
These changes are indicated in the djb_build_info.txt

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[hawkinsp]

We can't look at this PR without a signed CLA. (And I think the intent was that it wasn't to be merged as is anyway, more that it was a point for discussion.)

[durian888]

Hi Pete, Thank you for your email. You are correct – the pull request was more as a point of discussion. As to not signed the CLA – this has been blocked while my boss was trying to get a decision from his boss about whether I should sign as an individual or as an employee of the company. Currently I’m busy with other things so can’t look at the jax on windows stuff at the moment but I would dearly like to get back to it when I have some time. Dominic From: Peter Hawkins <[email protected]> Sent: Tuesday, June 23, 2020 10:11 AM To: google/jax <[email protected]> Cc: Barraclough, Dominic (ext. 414) <[email protected]>; Author <[email protected]> Subject: [EXTERNAL] Re: [google/jax] Changes made to hack a build on a win10 machine. (#2582) CAUTION: This email originated from outside of QVI. Do not click links or open attachments unless you recognize the sender and are expecting to receive this content from them. If you suspect the email is not legitimate, please forward it as an attachment to [email protected]<mailto:[email protected]> and delete it from your Inbox. We can't look at this PR without a signed CLA. (And I think the intent was that it wasn't to be merged as is anyway, more that it was a point for discussion.) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#2582 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIRK67W6N5VXPMQ4I3TCFDRYCZXBANCNFSM4L2ZNNHA>.

[hawkinsp]

FYI: #4843 added some initial support for building and running JAX on windows!