Your message dated Sun, 30 May 2010 19:44:14 +0200
with message-id <4c02a3ee.2070...@debian.org>
and subject line Re: gcc-4.1: do not compile old programs due not setting
HAS_STRERROR variable
has caused the Debian Bug report #463876,
regarding gcc-4.1: do not compile old programs due not setting HAS_STRERROR
variable
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
463876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.1
Version: 4.1.1-21
Severity: minor
I have an old (1999) program, i recompiled it for 64 bit, but gave strange
errors messages. i traced to the fact that the gcc i have now do not set the
HAS_STRERROR variable so the compiler included a not_so_up_to_date file.
Is this a feature or a bug ?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.23-1-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gcc-4.1 depends on:
ii binutils 2.17-3 The GNU assembler, linker and bina
ii cpp-4.1 4.1.1-21 The GNU C preprocessor
ii gcc-4.1-base 4.1.1-21 The GNU Compiler Collection (base
ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-21 GCC support library
ii libssp0 4.1.1-21 GCC stack smashing protection libr
Versions of packages gcc-4.1 recommends:
ii libc6-dev 2.3.6.ds1-13etch4 GNU C Library: Development Librari
pn libmudflap0-dev <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
that looks more than a configuration error or a usage error of gcc, not a bug
within gcc.
--- End Message ---
