From owner-freebsd-hackers Thu Sep 14 10:58:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id F373137B422 for ; Thu, 14 Sep 2000 10:58:41 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8EHw7T17902; Thu, 14 Sep 2000 10:58:07 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma017894; Thu, 14 Sep 2000 10:57:43 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id KAA12092; Thu, 14 Sep 2000 10:57:42 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009141757.KAA12092@bubba.whistle.com> Subject: Re: c++ error In-Reply-To: <200009141612.JAA02297@vashon.polstra.com> "from John Polstra at Sep 14, 2000 09:12:04 am" To: John Polstra Date: Thu, 14 Sep 2000 10:57:42 -0700 (PDT) Cc: hackers@freebsd.org, n@nectar.com X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > have both found edge cases where the gcc kluge loses. If you can > > come up with a reasonable test case that reproduces the problem, > > perhaps it can be PR'd to the GCC folks? > > Actually, I don't have a test case. I was only able to make it fail > when I moved out of /usr/include -- which disables the > gcc kludge. I hope that Archie will be able to come up with a test > case that demonstrates the failure. I was doing a build with DESTDIR=/usr/image and so in.h was actually being found in /usr/image/usr/include/netinet/in.h rather than the normal place, so this must be what happened to me as well. Ugh, I'm glad I got to skip C++ and go straight to Java :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message