What is the strategy to update eglibc?

DISCUSSION Kang Kai 5 participants 10 messages Oct 31, 2011 – Nov 17, 2011

Share & tools

Kang Kai

author

2011-10-31 02:17 UTC #0 lore raw

Hi Saul,

I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.

Could you give me some guide? Thank you!

Regards,
Kai

Kang Kai

author

2011-10-31 02:21 UTC #1 lore raw

Quoted 3 lines · Kang Kai

Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.

Hi Saul,

And right now is 2 commits behind the latest revision, do it worth to update right now? Thanks!

Quoted 10 lines

Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Saul Wold

2011-10-31 16:49 UTC #2 lore raw

Quoted 11 lines · Kang Kai

Quoted 6 lines · Kang Kai
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.
Hi Saul,
And right now is 2 commits behind the latest revision, do it worth to update right now?

Kai,

I know that Khem recently added the eglibc 2.14 recipe, but I think that we are still actually using the 2.13 recipe as defined by EGLIBCVERSION.

At this point, it might be good to know what's changed by those 2 commits and maybe do a full build and system test with EGLIBCVERSION set to 2.14 to find out if the problems are resolved. You might look back in the email list to mid-June to see what the original set of issues was.

Sau!

Quoted 18 lines

Thanks!
Quoted 10 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Kang Kai

author

2011-11-01 02:12 UTC #3 lore raw

Quoted 10 lines · Saul Wold

Quoted 9 lines · Kang Kai
Quoted 6 lines · Kang Kai
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.
Hi Saul,

Quoted 8 lines

Quoted 2 lines
And right now is 2 commits behind the latest revision, do it worth to update right now?
Kai,
I know that Khem recently added the eglibc 2.14 recipe, but I think that we are still actually using the 2.13 recipe as defined by EGLIBCVERSION.
At this point, it might be good to know what's changed by those 2 commits and maybe do a full build and system test with EGLIBCVERSION set to 2.14 to find out if the problems are resolved. You might look back in the email list to mid-June to see what the original set of issues was.

Thanks, Saul! I'll try that.

Quoted 23 lines

Sau!
Quoted 18 lines
Thanks!
Quoted 10 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Khem Raj

2011-11-16 21:45 UTC #4 lore raw

In reply to Kang Kai

Quoted 6 lines · Kang Kai

Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.

since release branches of eglibc only get bug fixes in ideal case it should be good at any revision. However if we have bug fixes that dont affect us immediately we do not tend to update the revision. If you find that some bug fix thats applied upstream is needed it certainly can be a reason to bump up srcrev given we do some level of build and runtime testing
with new revision.

Quoted 11 lines

Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Kang Kai

author

2011-11-17 02:39 UTC #5 lore raw

Quoted 7 lines · Khem Raj

Quoted 6 lines · Kang Kai
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.

Hi Khem,

Quoted 7 lines

since release branches of eglibc only get bug fixes in ideal case it should be good at any revision. However if we have bug fixes that dont affect us immediately we do not tend to update the revision. If you find that some bug fix thats applied upstream is needed it certainly can be a reason to bump up srcrev given we do some level of build and runtime testing
with new revision.

Thanks very much for your detailed explanation.
I check the changelog of eglibc 2.13 branch(latest is 15508), and they are some tiny updates except the revision 15226 that is same with current patch

glibc_bug_fix_12454.patch

And I made the rough tests of image-sato of qemu-x86 and qemu-arm and results are fine.

Regards,
Kai

Quoted 15 lines

Quoted 11 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Ni Qingliang

2011-11-17 02:43 UTC #6 lore raw

it looks like there is 2.14 bb file already, why the default eglibc stay on 2.13?

Quoted 51 lines · Kang Kai

Quoted 7 lines · Khem Raj
Quoted 6 lines · Kang Kai
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.
Hi Khem,
Quoted 7 lines
since release branches of eglibc only get bug fixes in ideal case it should be good at any revision. However if we have bug fixes that dont affect us immediately we do not tend to update the revision. If you find that some bug fix thats applied upstream is needed it certainly can be a reason to bump up srcrev given we do some level of build and runtime testing
with new revision.
Thanks very much for your detailed explanation.
I check the changelog of eglibc 2.13 branch(latest is 15508), and they are some tiny updates except the revision 15226 that is same with current patch
glibc_bug_fix_12454.patch
And I made the rough tests of image-sato of qemu-x86 and qemu-arm and results are fine.
Regards,
Kai
Quoted 11 lines
Quoted 11 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Signature · 3 lines

Yi Qingliang
[email protected]
https://niqingliang2003.wordpress.com

Khem Raj

2011-11-17 06:48 UTC #7 lore raw

Quoted 2 lines · Ni Qingliang

it looks like there is 2.14 bb file already, why the default eglibc stay on 2.13?

2.14 removed some functionality rpc which is used extensively alternative to use libtirpc is not sufficient atm. Therefore we readded the functionality into 2.14 recipes and they need testing. Some distros e.g. angstrom-bleeding use 2.14 but its not default in oe-core yet for same reasons that it needs to be
tested

Quoted 65 lines · Kang Kai

Quoted 47 lines · Khem Raj
Quoted 7 lines · Kang Kai
Quoted 6 lines
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.
Hi Khem,
Quoted 7 lines
since release branches of eglibc only get bug fixes in ideal case it should be good at any revision. However if we have bug fixes that dont affect us immediately we do not tend to update the revision. If you find that some bug fix thats applied upstream is needed it certainly can be a reason to bump up srcrev given we do some level of build and runtime testing
with new revision.
Thanks very much for your detailed explanation.
I check the changelog of eglibc 2.13 branch(latest is 15508), and they are some tiny updates except the revision 15226 that is same with current patch
glibc_bug_fix_12454.patch
And I made the rough tests of image-sato of qemu-x86 and qemu-arm and results are fine.
Regards,
Kai
Quoted 11 lines
Quoted 11 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Yi Qingliang
[email protected]
https://niqingliang2003.wordpress.com
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Ni Qingliang

2011-11-17 07:03 UTC #8 lore raw

Thanks for the explanation:)

Quoted 77 lines · Khem Raj

Quoted 2 lines · Ni Qingliang
it looks like there is 2.14 bb file already, why the default eglibc stay on 2.13?
2.14 removed some functionality rpc which is used extensively alternative to use libtirpc is not sufficient atm. Therefore we readded the functionality into 2.14 recipes and they need testing. Some distros e.g. angstrom-bleeding use 2.14 but its not default in oe-core yet for same reasons that it needs to be
tested
Quoted 65 lines · Kang Kai
Quoted 47 lines · Khem Raj
Quoted 7 lines · Kang Kai
Quoted 6 lines
Hi Saul,
I just want to update eglibc but eglibc is using its 2.14 branch and use svn commit revision "15225" as current version. Of course it is behind the latest svn revision, but I don't quit sure about which is the right revision to update eglibc.
Hi Khem,
Quoted 7 lines
since release branches of eglibc only get bug fixes in ideal case it should be good at any revision. However if we have bug fixes that dont affect us immediately we do not tend to update the revision. If you find that some bug fix thats applied upstream is needed it certainly can be a reason to bump up srcrev given we do some level of build and runtime testing
with new revision.
Thanks very much for your detailed explanation.
I check the changelog of eglibc 2.13 branch(latest is 15508), and they are some tiny updates except the revision 15226 that is same with current patch
glibc_bug_fix_12454.patch
And I made the rough tests of image-sato of qemu-x86 and qemu-arm and results are fine.
Regards,
Kai
Quoted 11 lines
Quoted 11 lines
Could you give me some guide? Thank you!
Regards,
Kai
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 4 lines
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Yi Qingliang
[email protected]
https://niqingliang2003.wordpress.com
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Signature · 3 lines

Yi Qingliang
[email protected]
https://niqingliang2003.wordpress.com

McClintock Matthew-B29882

2011-11-17 08:15 UTC #9 lore raw

In reply to Ni Qingliang

Quoted 2 lines · Ni Qingliang

it looks like there is 2.14 bb file already, why the default eglibc stay on 2.13?

../meta/conf/distro/include/tcmode-default.inc:PREFERRED_VERSION_eglibc

                  ?= "${EGLIBCVERSION}"

../meta/conf/distro/include/tcmode-default.inc:EGLIBCVERSION ?= "2.13"

Someone needs to bump the default version.

-M