Skip to contentSkip to conversation

Glibc 2.27

RFT Khem Raj 4 participants 7 messages Jan 27, 2018 – Jan 29, 2018

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

Hi All

glibc 2.27 is releasing soon in few weeks. I have put together the recipes for upgrade, along with fixes for some of packages that I ran into here

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/glibc-2.27

This has gotten limited testing. I plan to put the package fixes as we plough through. Please test this out in your setups and report problems or fixes ( preferred ) to get various packages working on 2.27 release

Thanks
-Khem

#1 lore raw

This one will be tough to integrate. Most of the packages depend on this one, which is critical one. On the very bottom. I would say, this is a big step, since here somewhere you should draw clear line. And this line will be the following: which releases you/YOCTO crew will support (back-port to) with Glibc 2.27, and which not?!

Zoran
_______

Quoted 18 lines · Khem Raj

Hi All

glibc 2.27 is releasing soon in few weeks. I have put together the recipes for upgrade, along with fixes for some of packages that I ran into here

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/glibc-2.27

This has gotten limited testing. I plan to put the package fixes as we plough through. Please test this out in your setups and report problems or fixes ( preferred ) to get various packages working on 2.27 release

Thanks
-Khem
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw
Quoted 6 lines · Zoran Stojsavljevic

This one will be tough to integrate. Most of the packages depend on this one, which is critical one. On the very bottom. I would say, this is a big step, since here somewhere you should draw clear line. And this line will be the following: which releases you/YOCTO crew will support (back-port to) with Glibc 2.27, and which not?!

This one will be easy to integrate: it goes into master and none of the stable releases. Stable releases only get upgrades after release is very limited situations.

Ross

#3 lore raw
Quoted 2 lines

Khem Raj writes: This has gotten limited testing. Burton Ross writes: This one will be easy to integrate.

Time Will Tell.

Zoran
_______

#4 lore raw
Quoted 5 lines · Zoran Stojsavljevic
Quoted 2 lines

Khem Raj writes: This has gotten limited testing. Burton Ross writes: This one will be easy to integrate.

Time Will Tell.

I guess I meant easy in that it just won't be going to stable releases. Obviously integration of a new C runtime release into master is never objectively easy.

Ross

#5 lore raw
Quoted 7 lines · Ross
Quoted 2 lines · On 29 January 2018 at 13:56, Zoran Stojsavljevic…

Khem Raj writes: This has gotten limited testing. Burton Ross writes: This one will be easy to integrate.

Quoted 6 lines

Time Will Tell.

I guess I meant easy in that it just won't be going to stable releases.  Obviously integration of a new C runtime release into master is never objectively easy.

We update tend to update some if not all the toolchain components at least once between releases.  So far, the small team of folks who clean up any issues with these updates have been successful.

- Armin

Quoted 4 lines

Ross

#6 lore raw
In reply to Khem Raj

The yocto autobuilder was idle so I fired it, fingers crossed :)

Quoted 20 lines · Khem Raj

Hi All

glibc 2.27 is releasing soon in few weeks. I have put together the recipes for upgrade, along with fixes for some of packages that I ran into here

http://git.openembedded.org/openembedded-core-contrib/log/?
h=kraj/glibc-2.27

This has gotten limited testing. I plan to put the package fixes as we plough through. Please test this out in your setups and report problems or fixes ( preferred ) to get various packages working on 2.27 release

Thanks
-Khem
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core