| Message ID | 1423408027-49694-2-git-send-email-Vincent.Riera@imgtec.com |
|---|---|
| State | Accepted |
| Headers | show |
Vicente, All, On 2015-02-08 15:07 +0000, Vicente Olivert Riera spake thusly: > - Add version 2.21 > - Add a hash value for it > > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Manually downloaded, and manually checked the hash: OK! :-) Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Regards, Yann E. MORIN. > --- > package/glibc/Config.in | 3 +++ > package/glibc/glibc.hash | 1 + > 2 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/package/glibc/Config.in b/package/glibc/Config.in > index 8c033f2..37e108e 100644 > --- a/package/glibc/Config.in > +++ b/package/glibc/Config.in > @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19 > config BR2_GLIBC_VERSION_2_20 > bool "2.20" > > +config BR2_GLIBC_VERSION_2_21 > + bool "2.21" > + > endchoice > > endif > diff --git a/package/glibc/glibc.hash b/package/glibc/glibc.hash > index 094bbda..f194de4 100644 > --- a/package/glibc/glibc.hash > +++ b/package/glibc/glibc.hash > @@ -6,3 +6,4 @@ md5 197836c2ba42fb146e971222647198dd eglibc-2.19-svnr25243.tar.bz2 > sha1 8013c1935b46fd50d2d1fbfad3b0af362b75fb28 eglibc-2.19-svnr25243.tar.bz2 > sha256 2d3997f588401ea095a0b27227b1d50cdfdd416236f6567b564549d3b46ea2a2 glibc-2.19.tar.xz > sha256 f84b6d42aecc288d593c397b0a3d02260a33ee686bce0c634eb9b32798f36ba5 glibc-2.20.tar.xz > +sha256 aeeb362437965a5d3f40b151094ca79def04a115bd363fdd4a9a0c69482923b8 glibc-2.21.tar.xz > -- > 1.7.1 >
Hi Vicente, On Sun, Feb 08, 2015 at 03:07:05PM +0000, Vicente Olivert Riera wrote: > - Add version 2.21 > - Add a hash value for it > > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> The glibc NEWS for the 2.21 release[1] include this: * The GNU C Library is now built with -Werror by default. This can be disabled by configuring with --disable-werror. I think we should add --disable-werror when configuring glibc 2.21. [1] https://sourceware.org/ml/libc-alpha/2015-02/msg00119.html baruch
On 2015-02-08 19:20 +0200, Baruch Siach spake thusly: > Hi Vicente, > > On Sun, Feb 08, 2015 at 03:07:05PM +0000, Vicente Olivert Riera wrote: > > - Add version 2.21 > > - Add a hash value for it > > > > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> > > The glibc NEWS for the 2.21 release[1] include this: > > * The GNU C Library is now built with -Werror by default. This can be > disabled by configuring with --disable-werror. Yup, I had seen this. And I think this is a good idea for such a critical piece of code. > I think we should add --disable-werror when configuring glibc 2.21. Why so? I think on the contrary we should keep the default, and only if we find issues then we can investigate as to whether this is a real error or not, and report that upstream. Granted, we usually remove -Werror from packages when they fail to build (and I am not a big fan of it, warnings should not be treated lightly), but only in that case. If the package builds fine with -Werror, we usually keep it. Regards, Yann E. MORIN.
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes: > - Add version 2.21 > - Add a hash value for it > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> > --- > package/glibc/Config.in | 3 +++ > package/glibc/glibc.hash | 1 + > 2 files changed, 4 insertions(+), 0 deletions(-) > diff --git a/package/glibc/Config.in b/package/glibc/Config.in > index 8c033f2..37e108e 100644 > --- a/package/glibc/Config.in > +++ b/package/glibc/Config.in > @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19 > config BR2_GLIBC_VERSION_2_20 > bool "2.20" > +config BR2_GLIBC_VERSION_2_21 > + bool "2.21" > + I noticed a few things in the release notes that might be of interest: * Port to Altera Nios II has been contributed by Mentor Graphics. So we should be able to build an internal glibc toolchain for nios2 now. * Support for MIPS o32 FPXX, FP64A and FP64 ABI Extensions. The original MIPS o32 hard-float ABI requires an FPU where double-precision registers overlay two consecutive single-precision registers. MIPS32R2 introduced a new FPU mode (FR=1) where double-precision registers extend the corresponding single-precision registers which is incompatible with the o32 hard-float ABI. The MIPS SIMD ASE and the MIPSR6 architecture both require the use of FR=1 making a transition necessary. New o32 ABI extensions enable users to migrate over time from the original o32 ABI through to the updated o32 FP64 ABI. To achieve this the dynamic linker now tracks the ABI of any loaded object and verifies that new objects are compatible. Mode transitions will also be requested as required and unsupportable objects will be rejected. The ABI checks include both soft and hard float ABIs for o32, n32 and n64. I'm not sure what the impact is of this exactly?
On 02/08/2015 10:55 PM, Peter Korsgaard wrote: >>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes: > > > - Add version 2.21 > > - Add a hash value for it > > > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> > > --- > > package/glibc/Config.in | 3 +++ > > package/glibc/glibc.hash | 1 + > > 2 files changed, 4 insertions(+), 0 deletions(-) > > > diff --git a/package/glibc/Config.in b/package/glibc/Config.in > > index 8c033f2..37e108e 100644 > > --- a/package/glibc/Config.in > > +++ b/package/glibc/Config.in > > @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19 > > config BR2_GLIBC_VERSION_2_20 > > bool "2.20" > > > +config BR2_GLIBC_VERSION_2_21 > > + bool "2.21" > > + > > I noticed a few things in the release notes that might be of interest: > > * Port to Altera Nios II has been contributed by Mentor Graphics. > > So we should be able to build an internal glibc toolchain for nios2 now. > > * Support for MIPS o32 FPXX, FP64A and FP64 ABI Extensions. > The original MIPS o32 hard-float ABI requires an FPU where double-precision > registers overlay two consecutive single-precision registers. MIPS32R2 > introduced a new FPU mode (FR=1) where double-precision registers extend the > corresponding single-precision registers which is incompatible with the > o32 hard-float ABI. The MIPS SIMD ASE and the MIPSR6 architecture both > require the use of FR=1 making a transition necessary. New o32 ABI > extensions enable users to migrate over time from the original o32 ABI > through to the updated o32 FP64 ABI. To achieve this the dynamic linker now > tracks the ABI of any loaded object and verifies that new objects are > compatible. Mode transitions will also be requested as required and > unsupportable objects will be rejected. The ABI checks include both soft and > hard float ABIs for o32, n32 and n64. > > I'm not sure what the impact is of this exactly? > Nothing you should be worried about. Just FPU ABI extensions for MIPS o32. This just makes it possible to link objects build for different FPU ABIs (assuming they are compatible). https://dmz-portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking ie everything works as expected with glibc-2.21
>>>>> "Markos" == Markos Chandras <Markos.Chandras@imgtec.com> writes: Hi, >> I'm not sure what the impact is of this exactly? >> > Nothing you should be worried about. Just FPU ABI extensions for MIPS > o32. This just makes it possible to link objects build for different FPU > ABIs (assuming they are compatible). > https://dmz-portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking > ie everything works as expected with glibc-2.21 Ok, thanks.
On 02/08/2015 07:55 PM, Peter Korsgaard wrote: >>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes: > > > - Add version 2.21 > > - Add a hash value for it > > > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> > > --- > > package/glibc/Config.in | 3 +++ > > package/glibc/glibc.hash | 1 + > > 2 files changed, 4 insertions(+), 0 deletions(-) > > > diff --git a/package/glibc/Config.in b/package/glibc/Config.in > > index 8c033f2..37e108e 100644 > > --- a/package/glibc/Config.in > > +++ b/package/glibc/Config.in > > @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19 > > config BR2_GLIBC_VERSION_2_20 > > bool "2.20" > > > +config BR2_GLIBC_VERSION_2_21 > > + bool "2.21" > > + > > I noticed a few things in the release notes that might be of interest: > > * Port to Altera Nios II has been contributed by Mentor Graphics. > > So we should be able to build an internal glibc toolchain for nios2 now. > Yes, as far as I understand, we should be able to build the toolchain now. Linux v3.19 has been just released, which includes the nios2 arch port. So we now have binutils, gcc, glibc and kernel support. FWIW, the glibc port was tested using Buildroot [1]! :) [1] http://sourceware-org.1504.n7.nabble.com/PATCH-0-4-Nios-II-port-submission-td265493.html
diff --git a/package/glibc/Config.in b/package/glibc/Config.in index 8c033f2..37e108e 100644 --- a/package/glibc/Config.in +++ b/package/glibc/Config.in @@ -38,6 +38,9 @@ config BR2_GLIBC_VERSION_2_19 config BR2_GLIBC_VERSION_2_20 bool "2.20" +config BR2_GLIBC_VERSION_2_21 + bool "2.21" + endchoice endif diff --git a/package/glibc/glibc.hash b/package/glibc/glibc.hash index 094bbda..f194de4 100644 --- a/package/glibc/glibc.hash +++ b/package/glibc/glibc.hash @@ -6,3 +6,4 @@ md5 197836c2ba42fb146e971222647198dd eglibc-2.19-svnr25243.tar.bz2 sha1 8013c1935b46fd50d2d1fbfad3b0af362b75fb28 eglibc-2.19-svnr25243.tar.bz2 sha256 2d3997f588401ea095a0b27227b1d50cdfdd416236f6567b564549d3b46ea2a2 glibc-2.19.tar.xz sha256 f84b6d42aecc288d593c397b0a3d02260a33ee686bce0c634eb9b32798f36ba5 glibc-2.20.tar.xz +sha256 aeeb362437965a5d3f40b151094ca79def04a115bd363fdd4a9a0c69482923b8 glibc-2.21.tar.xz
- Add version 2.21 - Add a hash value for it Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> --- package/glibc/Config.in | 3 +++ package/glibc/glibc.hash | 1 + 2 files changed, 4 insertions(+), 0 deletions(-)