From owner-freebsd-current Thu Jul 11 8:52:37 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 B788F37B400 for ; Thu, 11 Jul 2002 08:52:33 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B36743E3B for ; Thu, 11 Jul 2002 08:52:33 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.200] (vpn-client.marcuscom.com [10.2.1.200]) by creme-brulee.marcuscom.com (8.12.5/8.12.5) with ESMTP id g6BFqSFg003805; Thu, 11 Jul 2002 11:52:28 -0400 (EDT) (envelope-from marcus@marcuscom.com) Subject: Re: gcc-3.1 Mozilla Build Fails From: Joe Marcus Clarke To: Sheldon Hearn Cc: Dirk Engling , freebsd-current@FreeBSD.ORG In-Reply-To: <20020711071308.GE25502@starjuice.net> References: <20020711071308.GE25502@starjuice.net> Content-Type: multipart/mixed; boundary="=-Fd4NcyWA/bsLIQtHkm24" X-Mailer: Ximian Evolution 1.0.8 Date: 11 Jul 2002 11:52:14 -0400 Message-Id: <1026402735.357.17.camel@gyros.marcuscom.com> Mime-Version: 1.0 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 --=-Fd4NcyWA/bsLIQtHkm24 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 2002-07-11 at 03:13, Sheldon Hearn wrote: > On (2002/07/10 19:15), Dirk Engling wrote: > > > Maybe this would be more interesting to > > the mozilla guys but mozilla compiles on > > 2.95.3, so I think, the problem is related > > to gcc-3.1 > > As far as I know, ports/lang/gcc31 is still required to build mozilla. That, or stick the attached patch in mozilla/files. I'm still analyzing options to get Mozilla to build on alpha, though. Joe > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- PGP Key : http://www.marcuscom.com/pgp.asc --=-Fd4NcyWA/bsLIQtHkm24 Content-Disposition: attachment; filename*0=patch-xpcom_reflect_xptcall_src_md_unix_xptc_platforms_unixis; filename*1=h_x86.h Content-Transfer-Encoding: quoted-printable Content-Type: text/x-c-header; name*0=patch-xpcom_reflect_xptcall_src_md_unix_xptc_platforms_unixish_x8; name*1=6.h; charset=ISO8859-1 --- xpcom/reflect/xptcall/src/md/unix/xptc_platforms_unixish_x86.h.orig Fri= Jun 21 01:12:40 2002 +++ xpcom/reflect/xptcall/src/md/unix/xptc_platforms_unixish_x86.h Fri Jun = 21 01:41:51 2002 @@ -94,8 +94,16 @@ * gcc is that the system gcc defines __FreeBSD_cc_version. This variable * can also identify the period of time that 4.0-CURRENT used thunks. */ -#if defined(__FreeBSD_cc_version) && \ - (__FreeBSD_cc_version < 400002 || __FreeBSD_cc_version > 400003) + +/* It seems we need to use thunks in FreeBSD -CURRENT after gcc-3.1 was me= rged. + * This solves a problem wherein regxpcom and/or regchrome would seg fault + * after running for a while. This problem has also exhibited itself on=20 + * the alpha platform. Therefore, use thunks on all non-i386 versions of + * -stable and _all_ versions of -CURRENT that are using gcc-3.1. + */ +#if defined(__FreeBSD_cc_version) && defined(__i386__) && \ + (__FreeBSD_cc_version < 400002 || __FreeBSD_cc_version > 400003) && \ + (__FreeBSD_cc_version < 500003) #define CFRONT_STYLE_THIS_ADJUST #else #define THUNK_BASED_THIS_ADJUST --=-Fd4NcyWA/bsLIQtHkm24-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message