From owner-freebsd-multimedia Sat May 15 22:44:20 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id D19C014F28 for ; Sat, 15 May 1999 22:44:18 -0700 (PDT) (envelope-from finlayson@live.com) Received: from mg131-213.ricochet.net (mg131-213.ricochet.net [204.179.131.213]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id WAA09481 for ; Sat, 15 May 1999 22:44:07 -0700 (PDT) Message-Id: <3.0.5.16.19990515213535.271fff3c@shell7.ba.best.com> X-Sender: rsf@shell7.ba.best.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (16) Date: Sat, 15 May 1999 21:35:35 To: freebsd-multimedia@FreeBSD.ORG From: Ross Finlayson Subject: Binary incompatibility issues btw 2.2.x and 3.1? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What are the issues wrt. binary compatibility (or incompatibility) between FreeBSD 2.2.x, and FreeBSD 3.1? I've just had a report that some of my software - compiled and linked on a 2.2.5 machine - fails with a "Floating point exception" when run on 3.1-RELEASE. Is there anything obvious that I can be doing to prevent this (other than upgrading to 3.1 myself)? Ross. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message