From owner-freebsd-chat@FreeBSD.ORG Sat Jul 10 17:43:57 2004 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E147A16A4CE for ; Sat, 10 Jul 2004 17:43:57 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EDD443D55 for ; Sat, 10 Jul 2004 17:43:57 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from daleco.biz ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Sat, 10 Jul 2004 12:45:33 -0500 Message-ID: <40F02ADB.1050106@daleco.biz> Date: Sat, 10 Jul 2004 12:43:55 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040406 X-Accept-Language: en-us, en MIME-Version: 1.0 To: chat@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Jul 2004 17:45:33.0843 (UTC) FILETIME=[B3627E30:01C466A5] Subject: Where should I look for info about about port syntax error(s)? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 17:43:58 -0000 I'm trying to sort out an issue and am slightly overwhelmed by the number of possible mailing lists I should be looking at... I did "portupgrade -aRr" this week, and epiphany failed: In file included from ContentHandler.cpp:30: MozDownload.h:108: error: syntax error before `virtual' Line 108 in "MozDownload.h" is: virtual ~MozDownload(); That's rendered in my editor as a superscript "tilde". I figured this to be one of those "easy fixes" that I could perform; the tilde was the mistake, but removing it gets me nowhere. So many languages, so little time... Anyway, the question is, besides "recvsup your ports", where could I be reading (eg which mailing list) to catch up on these things? ports@? ports-bugs? advocacy? (j/k), I read that one, anyway ... Has this even been noticed or fixed, etc.? If you've a strategy for such things, what is it? Just curious ... I can live with the old epiphany, I imagine... KDK