From owner-freebsd-current Sat Nov 23 17:41:48 2002 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 7C70837B401; Sat, 23 Nov 2002 17:41:47 -0800 (PST) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [211.176.62.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685C143EAF; Sat, 23 Nov 2002 17:41:46 -0800 (PST) (envelope-from cjh@kr.FreeBSD.org) Received: from gradius.wdb.co.kr (daemon [211.176.62.31]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id B28C58F60B; Sun, 24 Nov 2002 10:41:43 +0900 (KST) Received: from localhost (localhost [127.0.0.1]) by gradius.wdb.co.kr (8.12.6/8.12.6) with ESMTP id gANFZf9A056470; Sun, 24 Nov 2002 00:35:42 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) Date: Sun, 24 Nov 2002 00:35:41 +0900 (KST) Message-Id: <20021124.003541.74695688.cjh@kr.FreeBSD.org> To: ports@freebsd.org Cc: current@freebsd.org Subject: Help fixing korean/byeoroo ports on -current From: CHOI Junho Organization: Korea FreeBSD Users Group X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 3.1rc2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I am trying to fix my ports to be built on -current. Almost all problems are gone(fix/update/etc...). But I have problem of korean/byeoroo ports. Can somebody look at more closer? http://bento.freebsd.org/errorlogs/5-full/ko-byeoroo-0.0.19990605.3_1.log The problem is that two header files have same "BOOL" definition. But #define for Xmd.h and typedef for objc.h. /usr/X11R6/include/X11/Xmd.h:158: redefinition of `BOOL' /usr/include/objc/objc.h:42: `BOOL' previously declared here What is a generally good solution for this? And, I checked this problem in my older -current desktop(September or October), but my current desktop doesn't have a problem(-current built at Nov 20); BOOL conflict are showed as just warning, and build go on. Is it the result of gcc updates? If so, don't I have to fix it? -- CHOI Junho FreeBSD Project Web Data Bank Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message