From owner-freebsd-ports@FreeBSD.ORG Sat May 17 06:39:08 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C00B37B401 for ; Sat, 17 May 2003 06:39:08 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07C2D43FA3 for ; Sat, 17 May 2003 06:39:07 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from witchspace.com ([80.3.251.242]) by mta03-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with SMTP id <20030517133905.SAYZ11246.mta03-svc.ntlworld.com@witchspace.com> for ; Sat, 17 May 2003 14:39:05 +0100 Received: (qmail 86745 invoked from network); 17 May 2003 13:39:05 -0000 Received: from unknown (HELO witchspace.com) (192.168.0.1) by dookie.witchspace.com with SMTP; 17 May 2003 13:39:05 -0000 Message-ID: <3EC63B78.6010203@witchspace.com> Date: Sat, 17 May 2003 14:39:04 +0100 From: Jonathan Belson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030509 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erik Trulsson References: <3EC53C6C.1040904@witchspace.com> <20030517121908.GA67369@rot13.obsecurity.org> <3EC62CC2.6090209@witchspace.com> <20030517130549.GA44928@falcon.midgard.homeip.net> In-Reply-To: <20030517130549.GA44928@falcon.midgard.homeip.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org cc: Kris Kennaway Subject: Re: FreeBSD Port: pornview-0.2.0.p.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2003 13:39:08 -0000 Erik Trulsson wrote: > That part of the structure is not the problem. The next part of this > structure is the problem. > > gchar stdout[GTK_MPLAYER_BUF_SIZE]; > gint stdout_size; > gchar stderr[GTK_MPLAYER_BUF_SIZE]; > gint stderr_size; True. > Not legitimate. The C standard itself says that stdin/stdout/stderr are > supposed to be macros and therefore this behaviour is expected Interesting...do you have a reference for this? Section 7.9.1 of the ANSI C spec says that stdin/stdout/stderr are expressions of type 'pointer to FILE', I can't see anything that says they're supposed to be macros. > The bug is in the application, not in FreeBSD, so, unfair or not, it > isn't FreeBSD that should be changed. I don't remember anyone stating that FreeBSD should be changed... --Jon http://www.witchspace.com