hi, dear developers, current glibc version what we used is 2.28 and it was launched at year 2018, it's too old for our system and there are little bugs which are not fixed. and lately gcc version was updated to 9.3, the glibc upstream community has already do a lot of works to adapt this change in the latest version. so in the next week, we will update glibc to the latest version 2.31. notice that this change will cause other package's build result which depend on the glibc. so I need all of your help to resolve this situlation by update your own package or use other ways. thx.
hi, dear developers, current glibc version what we used is 2.28 and it was launched at year 2018, it's too old for our system and there are little bugs which are not fixed. and lately gcc version was updated to 9.3, the glibc upstream community has already do a lot of works to adapt this change in the latest version. so in the next week, we will update glibc to the latest version 2.31. notice that this change will cause other package's build result which depend on the glibc. so I need all of your help to resolve this situlation by update your own package or use other ways. thx.
hi, dear developers, current glibc version what we used is 2.28 and it was launched at year 2018, it's too old for our system and there are few bugs which are not fixed. and lately gcc version was updated to 9.3, the glibc upstream community has already do a lot of works to adapt this change in the latest version. so in the next week, we will update glibc to the latest version 2.31. notice that this change will cause other package's build result which depend on the glibc. so I need all of your help to resolve this situlation by update your own package or use other ways. thx.
建议同步在glibc 提个issue 跟踪讨论过程，便于追溯
-----邮件原件----- 发件人: liqingqing via Dev [mailto:dev@openeuler.org] 发送时间: 2020年6月18日 11:01 收件人: dev@openeuler.org 抄送: Hushiyuan hushiyuan@huawei.com 主题: [Dev] glibc version update notification
hi, dear developers, current glibc version what we used is 2.28 and it was launched at year 2018, it's too old for our system and there are few bugs which are not fixed. and lately gcc version was updated to 9.3, the glibc upstream community has already do a lot of works to adapt this change in the latest version. so in the next week, we will update glibc to the latest version 2.31. notice that this change will cause other package's build result which depend on the glibc. so I need all of your help to resolve this situlation by update your own package or use other ways. thx.
_______________________________________________ Dev mailing list -- dev@openeuler.org To unsubscribe send an email to dev-leave@openeuler.org
Hi, gcc had updated to 9.3 last month, and I find there are unknown bugs with glibc 2.28, like https://gitee.com/open_euler/dashboard?issue_id=I1HAM.
I think it's a better way to upgrade glibc 2.31, but too many packages in openEuler related to glibc 2.28, such as binutils. So, may I create a branch to upgrade this package.
-
buque -
liqingqing -
Zhuyanpeng