Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2019-03-14 20:19:23 +0300

Sage gravatar image

Quick update on this.

We have glibc 2.25 in our devel now (https://git.merproject.org/mer-core/glibc/commits/master) and it will come out soon (not in the next release, but one after that). The reason for going to 2.25 was as there are new build requirements in newer releases that we need to solve first before going forward, but we are are already working on those so we could get even newer versions soon.

Quick list of next steps on this:

  • 2.26 requires gcc 4.9 or later, which is also in the works already https://git.merproject.org/mer-core/gcc/commits/master
  • 2.27 no new requirements that we do not yet meet
  • 2.28 requires make 4.0 or later
  • 2.29 requires gcc 5 or later
  • 2.30 (which is yet to be released) requires gcc 6.2 or later

Getting there one step at the time.

click to hide/show revision 2
No.2 Revision

Quick update on this.

We have glibc 2.25 in our devel now (https://git.merproject.org/mer-core/glibc/commits/master) and it will come out soon (not in the next release, but one after that). The reason for going to 2.25 was as there are new build requirements in newer releases that we need to solve first before going forward, but we are are already working on those so we could get even newer versions soon.

Quick list of next steps on this:

  • 2.26 requires gcc 4.9 or later, which is also in the works already https://git.merproject.org/mer-core/gcc/commits/master
  • 2.27 no new requirements that we do not yet meetmeet, WIP PR at https://git.merproject.org/mer-core/glibc/merge_requests/20
  • 2.28 requires make 4.0 or later
  • 2.29 requires gcc 5 or later
  • 2.30 (which is yet to be released) requires gcc 6.2 or later

Getting there one step at the time.