Date: Sat, 15 May 1999 22:25:25 +1200 From: Joe Abley <jabley@clear.co.nz> To: David Greenman <dg@root.com> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Nate Williams <nate@mt.sri.com>, hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: 3.1 binaries, 3.2 binaries...? Message-ID: <19990515222525.A11491@clear.co.nz> In-Reply-To: <199905142343.QAA11646@implode.root.com>; from David Greenman on Fri, May 14, 1999 at 04:43:30PM -0700 References: <199905142024.NAA04032@apollo.backplane.com> <199905142343.QAA11646@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
My stable machine now calls itself:
FreeBSD buddha.clear.net.nz 3.2-BETA FreeBSD 3.2-BETA #11: Fri May 14 19:24:02 NZST 1999 jabley@buddha.clear.net.nz:/usr/src/sys/compile/TIMELORD i386
In other words, the release version number has wrapped to 3.2 from 3.1
following a sup and build the other day.
I have been building the setiathome clients for 3.1 and 4.0 -- the 3.1
binary was previously built on this machine.
Presumably there have been _some_ changes between 3.1-RELEASE and 3.2-BETA
that would cause binaries compiled on 3.2 to have problems on 3.1. Does
anybody fancy
(a) testing a 3.2-compiled setiathome binary I just rolled, on a
3.1-RELEASE machine?
(b) taking over builds for FreeBSD 3.1 binaries, if it transpires there
is an incompatability? (I don't have a 3.1 machine any more)
Joe
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990515222525.A11491>