This bug was fixed in the package pytorch - 2.1.2+dfsg-4ubuntu1
---
pytorch (2.1.2+dfsg-4ubuntu1) oracular; urgency=medium
* Fix FTBFS with LLVM 18. (LP: #2067720)
- d/p/0011-Update-caffe2-with-LLVM-18-API-change-109408.patch:
- d/p/0012-Fix-build-for-llvm-18-115652.patch:
Package uploaded.
** Changed in: pytorch (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067720
Title:
pytorch 2.1.2+dfsg-4 FTBFS with llvm 18
To mana
I may have found the right set of patches to backport. I'm doing a PPA
build now to confirm, and will upload if everything goes OK.
** Changed in: pytorch (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: pytorch (Ubuntu)
Status: New => Triaged
--
Y
There are 2 other patches upstream related to LLVM-18. The whole set so
far is:
https://github.com/pytorch/pytorch/commit/20f394f10a389bcf13485929be8862f98ad4b322
https://github.com/pytorch/pytorch/commit/23bff71de4a6438e968a684f6fe8259180a6ab03
https://github.com/pytorch/pytorch/commit/f0d71de4ac
That commit is not enough. The build fails then with:
```
/usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCAFFE2_BUILD_MAIN_LIB
-DFMT_HEADER_ONLY=1 -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1
-DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS
-DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1
Looking at the upstream git repository, I found a fix for llvm >= 18:
https://github.com/pytorch/pytorch/pull/115652
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067720
Title:
pytorch 2.1.2+dfsg-4
