From owner-freebsd-current@FreeBSD.ORG Sat Jul 7 18:58:43 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A56D616A400 for ; Sat, 7 Jul 2007 18:58:43 +0000 (UTC) (envelope-from tmclaugh@sdf.lonestar.org) Received: from straycat.dhs.org (c-24-63-86-11.hsd1.ma.comcast.net [24.63.86.11]) by mx1.freebsd.org (Postfix) with ESMTP id 6482C13C448 for ; Sat, 7 Jul 2007 18:58:43 +0000 (UTC) (envelope-from tmclaugh@sdf.lonestar.org) Received: from [192.168.1.127] (bofh.straycat.dhs.org [192.168.1.127]) by straycat.dhs.org (8.13.8/8.13.8) with ESMTP id l67IWQC9014206 for ; Sat, 7 Jul 2007 14:32:28 -0400 (EDT) From: Tom McLaughlin To: FreeBSD Current Content-Type: text/plain Date: Sat, 07 Jul 2007 14:32:26 -0400 Message-Id: <1183833146.1978.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: sysutils/xsi not building on -CURRENT with new gcc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2007 18:58:43 -0000 Hi all, I updated sysutils/xsi to a new version and I just found it will not build on -CURRENT (July 2nd) in my tinderbox. I'm getting the following fail: if c++ -DHAVE_CONFIG_H -I. -I. -I. -I../lib -I/usr/local/include/libxml2 -I/usr/local/include -O1 -pipe -MT freebsd.o -MD -MP -MF ".deps/freebsd.Tpo" -c -o freebsd.o freebsd.cpp; then mv -f ".deps/freebsd.Tpo" ".deps/freebsd.Po"; else rm -f ".deps/freebsd.Tpo"; exit 1; fi In file included from /usr/include/sys/sx.h:37, from /usr/include/sys/filedesc.h:40, from /usr/include/sys/proc.h:44, from /usr/include/sys/user.h:47, from freebsd.cpp:35: /usr/include/sys/lock_profile.h:156: error: expected ',' or '...' before 'class' I'm trying to avoid setting USE_GCC on this port. How can I get around this issue? Thanks, tom -- | tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org | | FreeBSD http://www.FreeBSD.org |