Your message dated Tue, 10 Apr 2007 23:15:29 +0200 with message-id <20070410211529.GA16141@artemis> and subject line Bug#160840: libc6-dev: Work around for LLONG_MAX on 2.95.x in limits.h is never reached... has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libc6-dev: Work around for LLONG_MAX on 2.95.x in limits.h is never reached...
- From: James Antill <james@va.and.org>
- Date: Sat, 14 Sep 2002 00:25:14 -0400
- Message-id: <E17q4Uc-0001QR-00@backupmx1.and.org>
Package: libc6-dev Version: 2.2.5-11.1 Severity: normal In limits.h there is a work around for gcc-2.95.x not having LLONG_MAX defined, however it does... #if defined __GNUC__ && !defined _GCC_LIMITS_H_ /* `_GCC_LIMITS_H_' is what GCC's file defines. */ # include_next <limits.h> ...before the work around and so is never used because _GCC_LIMITS_H_ is always defined. The following program shows the behaviour... #define _GNU_SOURCE 1 #if 0 # include <limits.h> #else # include </usr/include/limits.h> #endif int main(void) { return (!LLONG_MAX); } ...changing the #if to 1 will make the program not compile. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux va 2.2.18pre11- #7 SMP Mon Feb 12 00:14:53 EST 2001 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages libc6-dev depends on: ii libc6 2.2.5-11.1 GNU C Library: Shared libraries an
--- End Message ---
--- Begin Message ---
- To: James Antill <james@va.and.org>, 160840-done@bugs.debian.org
- Subject: Re: Bug#160840: libc6-dev: Work around for LLONG_MAX on 2.95.x in limits.h is never reached...
- From: Pierre HABOUZIT <madcoder@debian.org>
- Date: Tue, 10 Apr 2007 23:15:29 +0200
- Message-id: <20070410211529.GA16141@artemis>
- In-reply-to: <E17q4Uc-0001QR-00@backupmx1.and.org>
- References: <E17q4Uc-0001QR-00@backupmx1.and.org>
gcc 2.95 is not part of debian anymore, and the snipplets now works with current gcc's On Sat, Sep 14, 2002 at 12:25:14AM -0400, James Antill wrote: > Package: libc6-dev > Version: 2.2.5-11.1 > Severity: normal > > In limits.h there is a work around for gcc-2.95.x not having LLONG_MAX > defined, however it does... > > #if defined __GNUC__ && !defined _GCC_LIMITS_H_ > /* `_GCC_LIMITS_H_' is what GCC's file defines. */ > # include_next <limits.h> > > ...before the work around and so is never used because _GCC_LIMITS_H_ is > always defined. The following program shows the behaviour... > > #define _GNU_SOURCE 1 > #if 0 > # include <limits.h> > #else > # include </usr/include/limits.h> > #endif > > int main(void) > { > return (!LLONG_MAX); > } > > > ...changing the #if to 1 will make the program not compile. > > -- System Information > Debian Release: 3.0 > Architecture: i386 > Kernel: Linux va 2.2.18pre11- #7 SMP Mon Feb 12 00:14:53 EST 2001 i686 > Locale: LANG=C, LC_CTYPE=C > > Versions of packages libc6-dev depends on: > ii libc6 2.2.5-11.1 GNU C Library: Shared libraries an > > > -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.orgAttachment: pgpKcbB7IIY02.pgp
Description: PGP signature
--- End Message ---