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.
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
PGP Key : http://www.marcuscom.com/pgp.asc
--- 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 merged.
+ * This solves a problem wherein regxpcom and/or regchrome would seg fault
+ * after running for a while. This problem has also exhibited itself on
+ * 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)