From owner-freebsd-current@FreeBSD.ORG Thu Apr 10 03:46:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D59637B401 for ; Thu, 10 Apr 2003 03:46:32 -0700 (PDT) Received: from relay9.melbpc.org.au (newglider.melbpc.org.au [203.12.152.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F3DC43F93 for ; Thu, 10 Apr 2003 03:46:30 -0700 (PDT) (envelope-from kpeter@melbpc.org.au) Received: from melbpc.org.au (b2-203-12-156-87.melbpc.org.au [203.12.156.87]) by relay9.melbpc.org.au (8.12.8/8.12.6) with ESMTP id h3AAkRZv013202 for ; Thu, 10 Apr 2003 20:46:27 +1000 (EST) (envelope-from kpeter@melbpc.org.au) Message-ID: <3E954B83.4070706@melbpc.org.au> Date: Thu, 10 Apr 2003 20:46:27 +1000 From: Peter Kostouros Organization: Melbourne PC User Group User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030315 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <200304101614.21262.agh@tpg.com.au> <200304100001.41318.cbiffle@safety.net> In-Reply-To: <200304100001.41318.cbiffle@safety.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.4(snapshot 20020706) (relay9) Subject: Re: KDE-3.1.1 build problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kpeter@melbpc.org.au List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 10:46:32 -0000 Hi It could also be stale C++ header files. I think the stale header file issue was discussed a few months ago. Try you luck with the archives. Cliff L. Biffle wrote: >On Thursday 10 April 2003 09:33 am, Alastair G. Hogge wrote: > > >>Hi all, >> >>I'm having problems building kdebase3 or kdelibs3 from the ports. >>Neither will build. I've been having this same problem ever since KDE-3 was >>ported. >> >> > >I've been building both cleanly for some time, but you might try opening the >offending file and inserting a 'namespace std;' after the header includes. > >This is not a fix, but it might force the module to build cleanly so you can >figure out what's wrong. > >-Cliff L. Biffle >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- Regards Peter As always the organisation disavows knowledge of this email