[glibc] 01/01: debian/libc6{, -mips32, -mipsn32}.symbols.mips64el: add symbols for files for mips64el.
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch sid
in repository glibc.
commit 78faf743a6094754f495179b570b50f25d6ea923
Author: Aurelien Jarno
Date: Tue Mar 8 13:14:30 2016 +0100
debian/libc6{,-mips32,-mipsn32}.symbols.mips64el: add symbols for files for
mips64el.
---
debian/changelog | 4 +++-
debian/libc6-mips32.symbols.mips64el | 5 +
debian/libc6-mipsn32.symbols.mips64el | 5 +
debian/libc6.symbols.mips64el | 5 +
4 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index b34eeeb..6f25837 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
glibc (2.22-2) UNRELEASED; urgency=medium
- *
+ [ Aurelien Jarno ]
+ * debian/libc6{,-mips32,-mipsn32}.symbols.mips64el: add symbols for files for
+mips64el.
-- Aurelien Jarno Mon, 07 Mar 2016 14:33:41 +0100
diff --git a/debian/libc6-mips32.symbols.mips64el
b/debian/libc6-mips32.symbols.mips64el
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mips32.symbols.mips64el
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
diff --git a/debian/libc6-mipsn32.symbols.mips64el
b/debian/libc6-mipsn32.symbols.mips64el
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6-mipsn32.symbols.mips64el
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
diff --git a/debian/libc6.symbols.mips64el b/debian/libc6.symbols.mips64el
new file mode 100644
index 000..5933230
--- /dev/null
+++ b/debian/libc6.symbols.mips64el
@@ -0,0 +1,5 @@
+#include "libc6.symbols.common"
+ld.so.1 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
+libc.so.6 #PACKAGE# #MINVER#
+#include "symbols.wildcards"
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-glibc/glibc.git
[glibc] branch sid updated (57bf0ee -> 78faf74)
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a change to branch sid
in repository glibc.
from 57bf0ee New changelog entry
new 78faf74 debian/libc6{,-mips32,-mipsn32}.symbols.mips64el: add
symbols for files for mips64el.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
debian/changelog | 4 +++-
debian/{libc6-mips64.symbols.mips => libc6-mips32.symbols.mips64el} | 0
debian/{libc6-mips64.symbols.mips => libc6-mipsn32.symbols.mips64el} | 0
debian/{libc6-mips64.symbols.mips => libc6.symbols.mips64el} | 0
4 files changed, 3 insertions(+), 1 deletion(-)
copy debian/{libc6-mips64.symbols.mips => libc6-mips32.symbols.mips64el} (100%)
copy debian/{libc6-mips64.symbols.mips => libc6-mipsn32.symbols.mips64el}
(100%)
copy debian/{libc6-mips64.symbols.mips => libc6.symbols.mips64el} (100%)
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-glibc/glibc.git
[glibc] 01/01: Update from upstream stable branch:
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch sid
in repository glibc.
commit 1d8a05c20ddc0fa019eefca431bda47ba0f0b949
Author: Aurelien Jarno
Date: Tue Mar 8 17:59:37 2016 +0100
Update from upstream stable branch:
* Update from upstream stable branch:
- Fix pow() precision on CPUs with fma4, and the corresponding testsuite
failures.
- debian/patches/s390/submitted-socketcall.diff: drop, merged upstream.
---
debian/changelog | 4 ++
debian/patches/git-updates.diff | 88 +--
debian/patches/s390/submitted-socketcall.diff | 31 --
debian/patches/series | 2 -
4 files changed, 86 insertions(+), 39 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 6f25837..f183c5a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,10 @@ glibc (2.22-2) UNRELEASED; urgency=medium
[ Aurelien Jarno ]
* debian/libc6{,-mips32,-mipsn32}.symbols.mips64el: add symbols for files for
mips64el.
+ * Update from upstream stable branch:
+- Fix pow() precision on CPUs with fma4, and the corresponding testsuite
+ failures.
+- debian/patches/s390/submitted-socketcall.diff: drop, merged upstream.
-- Aurelien Jarno Mon, 07 Mar 2016 14:33:41 +0100
diff --git a/debian/patches/git-updates.diff b/debian/patches/git-updates.diff
index 335c849..c6b108f 100644
--- a/debian/patches/git-updates.diff
+++ b/debian/patches/git-updates.diff
@@ -1,10 +1,27 @@
GIT update of git://sourceware.org/git/glibc.git/release/2.22/master from
glibc-2.22
diff --git a/ChangeLog b/ChangeLog
-index cb9124e..2ed60d6 100644
+index cb9124e..6e42a1e 100644
--- a/ChangeLog
+++ b/ChangeLog
-@@ -1,3 +1,355 @@
+@@ -1,3 +1,372 @@
++2015-09-24 Joseph Myers
++
++ [BZ #19003]
++ * sysdeps/x86_64/fpu/multiarch/Makefile (CFLAGS-e_pow-fma4.c): Add
++ $(config-cflags-nofma).
++
++2016-03-07 Hongjiu Zhang
++
++ * elf/sln.c (makesymlink): Change struct stat to stat64, and lstat
++ to lstat64.
++
++2016-03-02 Stefan Liebler
++
++ [BZ #19682]
++ * sysdeps/unix/sysv/linux/s390/s390-64/syscalls.list:
++ Remove socketcall syscalls.
++
+2016-03-01 Aurelien Jarno
+
+ * sysdeps/alpha/fpu/libm-test-ulps: Update ULPs.
@@ -361,10 +378,10 @@ index cb9124e..2ed60d6 100644
* version.h (RELEASE): Set to "stable".
diff --git a/NEWS b/NEWS
-index 4c31de7..81ceeae 100644
+index 4c31de7..4679258 100644
--- a/NEWS
+++ b/NEWS
-@@ -5,6 +5,30 @@ See the end for copying conditions.
+@@ -5,6 +5,31 @@ See the end for copying conditions.
Please send GNU C library bug reports via
[glibc] branch sid updated (78faf74 -> 1d8a05c)
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a change to branch sid
in repository glibc.
from 78faf74 debian/libc6{,-mips32,-mipsn32}.symbols.mips64el: add
symbols for files for mips64el.
new 1d8a05c Update from upstream stable branch:
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
debian/changelog | 4 ++
debian/patches/git-updates.diff | 88 +--
debian/patches/s390/submitted-socketcall.diff | 31 --
debian/patches/series | 2 -
4 files changed, 86 insertions(+), 39 deletions(-)
delete mode 100644 debian/patches/s390/submitted-socketcall.diff
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-glibc/glibc.git
glibc 2.22 testsuite issues on hppa
Dear HPPA porters, The glibc testsuite in version 2.22 which has been uploaded to sid 2 days ago fails to pass on both phantom and sibaris build daemons. There seems to be 3 failures that are regressions compared to glibc 2.21: FAIL: debug/backtrace-tst FAIL: nptl/tst-cancel9 FAIL: nptl/tst-cancelx9 These tests have not been modified between glibc 2.21 and glibc 2.22. In addition they are not listed in the expected failures list upstream [1]. Note that the compiler has been changed from gcc 4.9 to gcc 5, this might explain the failures, especially the first one. In addition libio/tst-atime fails on sibaris only. It might be a regression, but it is more likely a misconfiguration of the build daemon, with the build parition mounted with the noatime option. Can someone please investigate the issues? Thanks, Aurelien [1] https://sourceware.org/glibc/wiki/Release/2.22 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
glibc 2.22 testsuite issues on sparc64
Dear sparc64 porters, The glibc testsuite in version 2.22 which has been uploaded to sid 2 days ago fails to pass on both ravirin and landau build daemon, while it passes fine on my system. The ravirin build was done with glibc 2.22-0experimental3. There was a single failure: FAIL: nptl/tst-dlsym1 This test hasn't changed for year, and it is likely due to the fact the experimental chroot contains a mix of gcc 5 and gcc 6. The landau buildd tried to build twice glibc version 2.22-1 with both time exactly the same failures related to threads: FAIL: nptl/tst-cond10 FAIL: nptl/tst-cond16 FAIL: nptl/tst-cond17 FAIL: nptl/tst-cond18 FAIL: nptl/tst-cond25 FAIL: rt/tst-mqueue5 The error returned by some of these tests is "Resource temporarily unavailable". Given they are new issues that don't happen on ravirin nor on my system, it could be a kernel issue. Given I am unable to reproduce the issues, can someone please investigate them? Thanks, Aurelien [1] https://sourceware.org/glibc/wiki/Release/2.22 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Re: glibc 2.22 testsuite issues on hppa
On 08.03.2016 19:07, Aurelien Jarno wrote: > Dear HPPA porters, Hi Aurelien, > The glibc testsuite in version 2.22 which has been uploaded to sid 2 > days ago fails to pass on both phantom and sibaris build daemons. Thanks for the notice! > There seems to be 3 failures that are regressions compared to glibc > 2.21: > > FAIL: debug/backtrace-tst > FAIL: nptl/tst-cancel9 > FAIL: nptl/tst-cancelx9 > > These tests have not been modified between glibc 2.21 and glibc 2.22. In > addition they are not listed in the expected failures list upstream [1]. > Note that the compiler has been changed from gcc 4.9 to gcc 5, this > might explain the failures, especially the first one. I think thread cancellation does has problems. Anyway, maybe Dave wants to take a look at those...? > In addition libio/tst-atime fails on sibaris only. It might be a > regression, but it is more likely a misconfiguration of the build > daemon, with the build parition mounted with the noatime option. Both machines run the same kernel and builds are on SSD drives with ext4. Both have the build directories mounted with relatime mount option. So, it's strange. > Can someone please investigate the issues? Sure, we will look into it. Thanks, Helge > Thanks, > Aurelien > > [1] https://sourceware.org/glibc/wiki/Release/2.22 >
Bug#817207: glibc: kfreebsd-i386: illegal instruction in ld.so
Package: src:glibc Version: 2.22-1 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Hi, glibc/2.22 has a major problem on kfreebsd-i386. It built on the buildds, but the compiled ld-2.22.so is broken as seen on buildd finzi: https://buildd.debian.org/status/fetch.php?pkg=mksh&arch=kfreebsd-i386&ver=52c-1&stamp=1457437296 | dpkg: error processing archive /var/cache/apt/archives/libc-bin_2.22-1_kfreebsd-i386.deb (--unpack): | subprocess dpkg-deb --control was killed by signal (Illegal instruction) | Errors were encountered while processing: | /var/cache/apt/archives/libc-bin_2.22-1_kfreebsd-i386.deb Upgrading libc0.1 breaks pretty much everything: | Core was generated by `ld-2.22.so'. | Program terminated with signal 4, Illegal instruction. | (gdb) bt full | #0 0x0100622b in ?? () | No symbol table info available. | #1 0x62696c2f in ?? () | No symbol table info available. | #2 0x3833692f in ?? () | No symbol table info available. | #3 0x666b2d36 in ?? () | No symbol table info available. | #4 0x01001a90 in ?? () | No symbol table info available. | #5 0x in ?? () | No symbol table info available. That corresponds to the 'ud2' instruction in the disassembly below: | /* The stack is presently not executable, but this module | requires that it be executable. We must change the | protection of the variable which contains the flags used in | the mprotect calls. */ |#ifdef SHARED | if ((mode & (__RTLD_DLOPEN | __RTLD_AUDIT)) == __RTLD_DLOPEN) |51fc: 8b 45 14mov0x14(%ebp),%eax |51ff: 25 00 00 00 88 and$0x8800,%eax |5204: 3d 00 00 00 80 cmp$0x8000,%eax |5209: 0f 84 b9 01 00 00 je 53c8 <_dl_map_object_from_fd+0x1258> |} | __stack_prot |= PROT_READ|PROT_WRITE|PROT_EXEC; | __mprotect ((void *) p, s, PROT_READ); |} | else |__stack_prot |= PROT_READ|PROT_WRITE|PROT_EXEC; |520f: 8b 85 70 ff ff ff mov-0x90(%ebp),%eax |5215: 83 88 1c ff ff ff 07orl$0x7,-0xe4(%eax) |521c: e8 af 2e 01 00 call 180d0 <__x86.get_pc_thunk.cx> |5221: 81 c1 df cd 01 00 add$0x1cddf,%ecx |5227: 29 d9 sub%ebx,%ecx |5229: 74 02 je 522d <_dl_map_object_from_fd+0x10bd> |522b: 0f 0b ud2 | |#ifdef check_consistency | check_consistency (); |#endif | | errval = (*GL(dl_make_stack_executable_hook)) (stack_endp); |522d: 8b 8d 70 ff ff ff mov-0x90(%ebp),%ecx kFreeBSD 10 disallows executable stacks by default. It can be allowed again by sysctl kern.elf32.nxstack=0, but it would be better if glibc didn't need this. I wonder why this issue wasn't seen on kfreebsd-amd64 since executable stacks are not allowed there either. Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-i386 (i386) Kernel: kFreeBSD 10.1-0-amd64 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) signature.asc Description: Digital signature
Re: glibc 2.22 testsuite issues on hppa
On 2016-03-08, at 2:57 PM, Helge Deller wrote: >> There seems to be 3 failures that are regressions compared to glibc >> 2.21: >> >> FAIL: debug/backtrace-tst >> FAIL: nptl/tst-cancel9 >> FAIL: nptl/tst-cancelx9 >> >> These tests have not been modified between glibc 2.21 and glibc 2.22. In >> addition they are not listed in the expected failures list upstream [1]. >> Note that the compiler has been changed from gcc 4.9 to gcc 5, this >> might explain the failures, especially the first one. > > I think thread cancellation does has problems. > Anyway, maybe Dave wants to take a look at those...? The cancellation tests have always been somewhat problematic. Helge wrote a couple of weeks ago and he thought there was an unwind issue. We will investigate as soon as possible. At the moment, we are trying to debug a kernel/gcc bug that causes a bootstrap failure. I would guess the new optimizations in gcc 5 are causing problems. Dave -- John David Anglin dave.ang...@bell.net
Bug#817207: glibc: kfreebsd-i386: illegal instruction in ld.so
Steven Chamberlain wrote: > Upgrading libc0.1 breaks pretty much everything: Actually not everything. It broke the buildd though, because dpkg-deb stopped working. This was from dpkg-deb: > | Core was generated by `ld-2.22.so'. > | Program terminated with signal 4, Illegal instruction. > | (gdb) bt full > | #0 0x0100622b in ?? () > | No symbol table info available. > | #1 0x62696c2f in ?? () > | No symbol table info available. > | #2 0x3833692f in ?? () > | No symbol table info available. > | #3 0x666b2d36 in ?? () > | No symbol table info available. > | #4 0x01001a90 in ?? () > | No symbol table info available. > | #5 0x in ?? () > | No symbol table info available. It fails trying to map shared object liblzma.so.5: | 2494 ld.so.1 NAMI "/usr/bin/dpkg-deb" | ... | 2494 ld.so.1 NAMI "/lib/i386-kfreebsd-gnu/libz.so.1" | 2494 ld.so.1 NAMI "/lib/i386-kfreebsd-gnu/liblzma.so.5" | ... | 2494 ld.so.1 PSIG SIGILL SIG_DFL code=ILL_PRVOPC There is something special about liblzma.so.5: | STACK off0x vaddr 0x paddr 0x align 2**2 | filesz 0x memsz 0x flags rwx It requires a writable and executable stack! which is rather rare, and probably should be fixed in the affected libraries. The kfreebsd buildds have disallowed executable stacks since DebConf15 though. I'm not sure why glibc 2.22 causes any regression here; this code has not changed since 2.21, but maybe something related to DEFAULT_STACK_PERMS, PF_X or PT_GNU_STACK has changed recently. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
