From owner-freebsd-current@FreeBSD.ORG Mon May 24 16:06:13 2004 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 C6D3416A525; Mon, 24 May 2004 16:06:13 -0700 (PDT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 325CF43D1F; Mon, 24 May 2004 16:06:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.12.11/8.12.11) with ESMTP id i4ON5pZc011168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 May 2004 16:05:51 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.11/8.12.11/Submit) id i4ON5oSm011091; Mon, 24 May 2004 16:05:50 -0700 (PDT) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040524203547.939D379004A@ws1-14.us4.outblaze.com> Date: Mon, 24 May 2004 16:05:50 -0700 (PDT) From: John Polstra To: "P.D. Seniura" X-Bogosity: No, tests=bogofilter, spamicity=0.215375, version=0.14.5 cc: freebsd-current@freebsd.org cc: Alex Dupre cc: freebsd-ports@freebsd.org Subject: Re: lang/ezm3 "runtime error: Segmentation violation..." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 24 May 2004 23:06:14 -0000 On 24-May-2004 P.D. Seniura wrote: > ----- Original Message ----- > From: Alex Dupre > Date: Mon, 24 May 2004 19:00:30 +0200 > To: Paul Seniura > Subject: Re: lang/ezm3 "runtime error: Segmentation violation..." > >> Paul Seniura wrote: >> > I'm including a snip of my portupgrade log for lang/ezm3 below. >> > I can't get past this point. Could someone offer ideas, please? >> >> Same problem here with -O2, no problem with plain -O gcc flag. > > Thank you for helping. > > Do we blame the code or the compiler? Blame the code in this case. It's a known issue with ezm3. It probably will not be fixed soon. John