[arch-general] LLVM update blocker?
Hi, I'd like to ask if there's anything that is holding back upgrading the LLVM package to 3.8.0. (The package is already flaged out-of-date and I don't think this worth opening an issue for so I decided to ask here...) I'm aware that LLVM is famous for breaking API at every release and I know that clang is currently suffering from the GCC abi_tag issue so I can understand if some of these issues are holding back the upgrade. However, I would still like to know what is the issue (if any) since it would help me planing for the llvm-julia package and related stuff. Thanks, Yichao Yu
On 04/09/2016 07:26 PM, Yichao Yu wrote:
Hi,
I'd like to ask if there's anything that is holding back upgrading the LLVM package to 3.8.0. (The package is already flaged out-of-date and I don't think this worth opening an issue for so I decided to ask here...)
I'm aware that LLVM is famous for breaking API at every release and I know that clang is currently suffering from the GCC abi_tag issue so I can understand if some of these issues are holding back the upgrade. However, I would still like to know what is the issue (if any) since it would help me planing for the llvm-julia package and related stuff.
Thanks,
Yichao Yu
The maintainer is not going to be available for a while, so who knows when other Developers will have time/interest in updating his stuff. https://lists.archlinux.org/pipermail/arch-dev-public/2016-March/027795.html -- Eli Schwartz
On Sat, Apr 9, 2016 at 10:45 PM, Eli Schwartz <eschwartz93@gmail.com> wrote:
On 04/09/2016 07:26 PM, Yichao Yu wrote:
Hi,
I'd like to ask if there's anything that is holding back upgrading the LLVM package to 3.8.0. (The package is already flaged out-of-date and I don't think this worth opening an issue for so I decided to ask here...)
I'm aware that LLVM is famous for breaking API at every release and I know that clang is currently suffering from the GCC abi_tag issue so I can understand if some of these issues are holding back the upgrade. However, I would still like to know what is the issue (if any) since it would help me planing for the llvm-julia package and related stuff.
Thanks,
Yichao Yu
The maintainer is not going to be available for a while, so who knows when other Developers will have time/interest in updating his stuff.
https://lists.archlinux.org/pipermail/arch-dev-public/2016-March/027795.html
OK, thanks for the info. I'll just assume it will not be upgraded in a while.
-- Eli Schwartz
On 04/10/2016 08:07 AM, Yichao Yu wrote:
On Sat, Apr 9, 2016 at 10:45 PM, Eli Schwartz <eschwartz93@gmail.com> wrote:
The maintainer is not going to be available for a while, so who knows when other Developers will have time/interest in updating his stuff.
https://lists.archlinux.org/pipermail/arch-dev-public/2016-March/027795.html
OK, thanks for the info. I'll just assume it will not be upgraded in a while.
See: https://lists.archlinux.org/pipermail/arch-dev-public/2016-April/027914.html -- Eli Schwartz
On Sun, Apr 17, 2016 at 12:51 AM, Eli Schwartz <eschwartz93@gmail.com> wrote:
On 04/10/2016 08:07 AM, Yichao Yu wrote:
On Sat, Apr 9, 2016 at 10:45 PM, Eli Schwartz <eschwartz93@gmail.com> wrote:
The maintainer is not going to be available for a while, so who knows when other Developers will have time/interest in updating his stuff.
https://lists.archlinux.org/pipermail/arch-dev-public/2016-March/027795.html
OK, thanks for the info. I'll just assume it will not be upgraded in a while.
See: https://lists.archlinux.org/pipermail/arch-dev-public/2016-April/027914.html
Thanks for the update.
-- Eli Schwartz
participants (2)
-
Eli Schwartz
-
Yichao Yu