| 6 Mar 2023 |
 SomeoneSerge (matrix works sometimes) | Oh! I like the name! Wait, last run was two years ago https://github.com/pytorch/builder/actions/workflows/build-pytorch-wheels.yml | 22:33:36 |
 hexa | yep, they prepare the build env through that | 22:33:58 |
| hexa | get centos, llvm 9.0.1, enable some centos repo, yum update, | 22:35:12 |
| hexa |
yum install -y wget curl perl util-linux xz bzip2 git patch which zlib-devel
| 22:35:13 |
| hexa | then | 22:35:25 |
| hexa |
yum install -y autoconf automake make cmake gdb gcc gcc-c++
| 22:35:26 |
| hexa |
yum install -y openssl-devel zlib-devel bzip2-devel ncurses-devel sqlite-devel readline-devel tk-devel gdbm-devel libpcap-devel xz-devel libffi-devel
| 22:35:34 |
| SomeoneSerge (matrix works sometimes) | And that is how we get AI | 22:35:48 |
| hexa | then they use scripts to install
- openssl
- libpng
- jni
- patchelf (yay)
- mkl
- conda (nay)
| 22:36:17 |
| hexa | nice | 22:36:50 |
| hexa | yeah, I'm tired. | 22:37:23 |
| hexa | https://github.com/pytorch/builder/blob/3eb479e831d3d8bd80d6c71203a51a4d22f93c7f/libtorch/Dockerfile#L34 | 22:39:22 |
| hexa | that is that docker file | 22:39:26 |
| SomeoneSerge (matrix works sometimes) | Half way there, we just need to know what to run inside the container | 22:40:01 |
| hexa | maybe https://github.com/pytorch/builder/blob/3eb479e831d3d8bd80d6c71203a51a4d22f93c7f/wheel/build_wheel.sh | 22:40:21 |
| SomeoneSerge (matrix works sometimes) | I'm beginning to wonder if we should go back to the pytorch repo | 22:40:30 |
| SomeoneSerge (matrix works sometimes) | In reply to @hexa:lossy.network
maybe https://github.com/pytorch/builder/blob/3eb479e831d3d8bd80d6c71203a51a4d22f93c7f/wheel/build_wheel.sh This one is, if we trust pytorch discourse, for Darwin | 22:40:54 |
| SomeoneSerge (matrix works sometimes) | And there's manywheel for Linux | 22:41:02 |
| SomeoneSerge (matrix works sometimes) | But all of these scripts are full of conditional flags | 22:41:10 |
| SomeoneSerge (matrix works sometimes) | So, somewhere out there something must call them with certain flags set on 🤔 | 22:41:31 |
| hexa | https://github.com/pytorch/builder/blob/3eb479e831d3d8bd80d6c71203a51a4d22f93c7f/wheel/build_all.sh#L12 | 22:42:10 |
| hexa | yep, darwin | 22:42:13 |
| SomeoneSerge (matrix works sometimes) | .github/workflows/_binary-build-linux.yml
203: docker exec -t "${container_name}" bash -c "source ${BINARY_ENV_FILE} && bash /builder/${{ inputs.PACKAGE_TYPE }}/build.sh"
| 22:44:35 |
| SomeoneSerge (matrix works sometimes) | .github/workflows/_linux-build.yml
161: docker exec -t "${container_name}" sh -c '.jenkins/pytorch/build.sh'
| 22:45:01 |
| SomeoneSerge (matrix works sometimes) | Yes, I think this is the right one: https://github.com/pytorch/pytorch/blob/39e8311a29b5713c8858cab73a8f713a7f3d531c/.github/workflows/_binary-build-linux.yml#L205
...but they still take the flags from elsewhere and just propagate them | 22:51:02 |
| SomeoneSerge (matrix works sometimes) | aaaaaand 0 workflows run https://github.com/pytorch/pytorch/actions/workflows/_binary-build-linux.yml | 22:51:55 |
| hexa | yeah, why would they run that 😄 | 22:52:07 |
| SomeoneSerge (matrix works sometimes) | https://github.com/pytorch/pytorch/actions/runs/4337823562 | 22:54:01 |
| SomeoneSerge (matrix works sometimes) | Here https://github.com/pytorch/pytorch/actions/runs/4337823562/jobs/7574087583#step:14:305 | 22:55:00 |
| SomeoneSerge (matrix works sometimes) | -DBUILD_LIBTORCH_CPU_WITH_DEBUG=0
Ok, how do we check we don't have any debug symbols in our libs?
| 22:55:59 |
