[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#267205: marked as done (xutils: [makedepend] spuriously complains about standards-compliant whitespace being non-portable)

Your message dated Sun, 18 Feb 2007 17:19:55 +0100
with message-id <45D87CAB.4070102@ens-lyon.org>
and subject line Bug#267205: xutils: [makedepend] spuriously complains about standards-compliant whitespace being non-portable
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 --- 
Package: libc6-dev
Version: 2.3.2.ds1-16
Severity: normal
File: /usr/include/gnu/stubs.h

This file uses non-portable whitespace, to wit:

#ifdef _LIBC
 #error Applications may not define the macro _LIBC
#endif

The leading space before the hash mark is not correct.

# error Applications may not define the macro _LIBC

would be better (and portable).

This causes tools like X11's "makedepend" script to howl.  A lot.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.25-powerpc-smp
Locale: LANG=C, LC_CTYPE=en_US.UTF-8

Versions of packages libc6-dev depends on:
ii  libc6                2.3.2.ds1-16        GNU C Library: Shared libraries an
ii  linux-kernel-headers 2.5.999-test7-bk-17 Linux Kernel Headers for developme

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:1.0.1-1.

Fixed upstream 18months ago, already in Etch.
http://gitweb.freedesktop.org/?p=xorg/util/makedepend.git;a=commit;h=275c17136006f9d3929c9547642f1ed3f95d5683

Brice

--- End Message ---
Reply to: