Your message dated Wed, 28 Nov 2001 18:28:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line not a bug
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Oct 2001 22:25:54 +0000
>From [EMAIL PROTECTED] Sun Oct 07 17:25:54 2001
Return-path: <[EMAIL PROTECTED]>
Received: from b55a8.pppool.de (atterer.net) [213.7.85.168] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 15qMMr-00051k-00; Sun, 07 Oct 2001 17:25:54 -0500
Received: from richard by atterer.net with local (Exim 3.32 #1 (Debian))
        id 15qJ75-0005cz-00; Sun, 07 Oct 2001 20:57:23 +0200
From: Richard Atterer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-3.0: Weird behaviour with -I/usr/include
X-Reportbug-Version: 1.28
X-Mailer: reportbug 1.28
Date: Sun, 07 Oct 2001 20:57:22 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]

Package: gcc-3.0
Version: 1:3.0.1-0pre010811
Severity: normal

Hello,

I encountered some very strange behaviour when using -I/usr/include. 
Obviously, it doesn't make much sense to supply this switch on the
command line, but in any case gcc's reaction is wrong. (I came across
this because libwww-config happens to include -I/usr/include in its
--cflags output.)

> echo '#include <string>' >x.cc 
> touch string.hh
> g++-3.0 -I/usr/include -c x.cc -o x.o
In file included from /usr/include/g++-v3/bits/char_traits.h:39,
                 from /usr/include/g++-v3/bits/std_string.h:41,
                 from /usr/include/g++-v3/string:31,
                 from x.cc:1:
/usr/include/g++-v3/bits/std_cstring.h:40:25: string.h: No such file or 
directory
In file included from /usr/include/g++-v3/bits/char_traits.h:39,
                 from /usr/include/g++-v3/bits/std_string.h:41,
                 from /usr/include/g++-v3/string:31,
                 from x.cc:1:
/usr/include/g++-v3/bits/std_cstring.h:68: `memcpy' not declared
/usr/include/g++-v3/bits/std_cstring.h:69: `memmove' not declared
/usr/include/g++-v3/bits/std_cstring.h:70: `strcpy' not declared
/usr/include/g++-v3/bits/std_cstring.h:71: `strncpy' not declared
/usr/include/g++-v3/bits/std_cstring.h:72: `strcat' not declared
/usr/include/g++-v3/bits/std_cstring.h:73: `strncat' not declared
[...]

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux elessar 2.2.19 #1 Mon May 21 19:42:05 CEST 2001 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages gcc-3.0 depends on:
ii  binutils              2.11.90.0.31-1     The GNU assembler, linker and bina
ii  cpp-3.0               1:3.0.1-0pre010811 The GNU C preprocessor.
ii  gcc-3.0-base          1:3.0.1-0pre010811 The GNU Compiler Collection (base 
ii  libc6                 2.2.4-1            GNU C Library: Shared libraries an
ii  libgcc1               1:3.0.1-0pre010811 GCC support library.


---------------------------------------
Received: (at 114795-done) by bugs.debian.org; 28 Nov 2001 18:28:07 +0000
>From [EMAIL PROTECTED] Wed Nov 28 12:28:07 2001
Return-path: <[EMAIL PROTECTED]>
Received: from parcelfarce.linux.theplanet.co.uk (www.linux.org.uk) 
[195.92.249.252] (exim)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 1699RH-0008SY-00; Wed, 28 Nov 2001 12:28:07 -0600
Received: from willy by www.linux.org.uk with local (Exim 3.33 #5)
        id 1699RG-0005Oe-00
        for [EMAIL PROTECTED]; Wed, 28 Nov 2001 18:28:06 +0000
Date: Wed, 28 Nov 2001 18:28:06 +0000
From: Matthew Wilcox <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: not a bug
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender:  <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]


upstream does not consider this to be a bug, see
http://gcc.gnu.org/ml/gcc/2001-07/msg00307.html

-- 
Revolutions do not require corporate support.


Reply via email to