Date: Mon, 5 May 2008 16:52:20 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: hackers@freebsd.org Subject: binary compatibility query Message-ID: <5f67a8c40805051352x6c7ed348v4c6648e708dfdba5@mail.gmail.com> In-Reply-To: <5f67a8c40805051351i19930db7le0a1bcce7c6276b8@mail.gmail.com> References: <4dcb5abd0805050540m292b319aw52aa2cb8ba018e12@mail.gmail.com> <481F0DB3.9070505@FreeBSD.org> <481F48EE.3050806@elischer.org> <5f67a8c40805051351i19930db7le0a1bcce7c6276b8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD Hackers, > > > > > > I have a general question about the compatibility of FreeBSD binaries > > > within major releases. If I build a binary for a given release of > > > FreeBSD can I make a reasonable guarantee that the binary will run on > > > > As a datapoint, I have been using cistron-radiusd for some time. Recently, I got a new system to run it and compiled the port on it. The compiled port didn't work on amd64 (or my configuration didn't jive with the new version of the daemon). So I grabbed the i386 binary that was built likely around 4.6 to 4.8 FreeBSD (I don't even remember --- it was so long ago). and dropped it on the amd64 7.0-RELEASE system. The binary is dynamically linked (albeit not depending on other packaged libraries) and I had the compat4, compat5 and compat6 ports installed on the new machine. It runs (and is still running) just fine. That's pretty good for compatibility.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40805051352x6c7ed348v4c6648e708dfdba5>