Bug#480093: sys/user.h broken on (at least) hppa
On Wed, May 7, 2008 at 10:24 PM, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote: > On Thu, May 08, 2008 at 03:16:38AM +0200, Frank Lichtenheld wrote: > > Package: libc6-dev > > Version: 2.7-10 > > Severity: important > > > > On HPPA sys/user.h only contains "#include " > > which doesn't do anything useful since linux-libc-dev doesn't > > contain user.h (except on arm/armel for whatever reason). > > > > On i386 sys/user.h actually contains something useful. > > Just curious, but what breaks? > > is a somewhat dodgy header; most software should not be > using it. Also, its contents are completely platform-dependent. I haven't seen anything break on hppa. I've been testing with a recent kernel that doesn't have a user.h. I checked in a blank sys/user.h for hppa upstream ports. http://sourceware.org/cgi-bin/cvsweb.cgi/ports/sysdeps/unix/sysv/linux/hppa/sys/user.h?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=glibc As far as I know gdb was the only user, and the hppa gdb port didn't use user.h. Cheers, Carlos. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480093: sys/user.h broken on (at least) hppa
On Thu, May 08, 2008 at 03:16:38AM +0200, Frank Lichtenheld wrote: > Package: libc6-dev > Version: 2.7-10 > Severity: important > > On HPPA sys/user.h only contains "#include " > which doesn't do anything useful since linux-libc-dev doesn't > contain user.h (except on arm/armel for whatever reason). > > On i386 sys/user.h actually contains something useful. Just curious, but what breaks? is a somewhat dodgy header; most software should not be using it. Also, its contents are completely platform-dependent. -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480093: sys/user.h broken on (at least) hppa
Package: libc6-dev Version: 2.7-10 Severity: important On HPPA sys/user.h only contains "#include " which doesn't do anything useful since linux-libc-dev doesn't contain user.h (except on arm/armel for whatever reason). On i386 sys/user.h actually contains something useful. Haven't checked any other arches, yet. Gruesse, Frank Lichtenheld -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable'), (900, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc6-dev depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii linux-libc-dev2.6.25-1 Linux Kernel Headers for developme Versions of packages libc6-dev recommends: ii gcc [c-compiler] 4:4.2.3-8 The GNU C compiler ii gcc-3.4 [c-compiler] 3.4.6-7The GNU C compiler ii gcc-4.1 [c-compiler] 4.1.2-22 The GNU C compiler ii gcc-4.2 [c-compiler] 4.2.3-5The GNU C compiler ii gcc-4.3 [c-compiler] 4.3.0-4The GNU C compiler -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479952: libc6/s390 - __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
Package: libc6 Version: 2.7-10 Severity: important On Wed, May 07, 2008 at 09:34:12AM +0200, Matthias Klose wrote: > the build failure on s390 is unexpected; is it possible to extract a > test case? | java: pthread_mutex_lock.c:71: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. So another package failed about that (after mono and libto$bla). It looks like a race condition somewhere in the libpthread. Bastian -- The more complex the mind, the greater the need for the simplicity of play. -- Kirk, "Shore Leave", stardate 3025.8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
