Date: Wed, 21 Feb 2001 17:46:01 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Warner Losh <imp@harmony.village.org> Cc: Kris Kennaway <kris@obsecurity.org>, mi@aldan.algebra.com, arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010221174601.A9511@Odin.AC.HMC.Edu> In-Reply-To: <200102220128.f1M1SbW01360@harmony.village.org>; from imp@harmony.village.org on Wed, Feb 21, 2001 at 06:28:37PM -0700 References: <20010221153037.A16193@Odin.AC.HMC.Edu> <20010221123835.A59024@mollari.cthul.hu> <200102212306.f1LN6Ov33309@misha.privatelabs.com> <20010221151827.A61818@mollari.cthul.hu> <20010221153037.A16193@Odin.AC.HMC.Edu> <200102220128.f1M1SbW01360@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 21, 2001 at 06:28:37PM -0700, Warner Losh wrote: > In message <20010221153037.A16193@Odin.AC.HMC.Edu> Brooks Davis writes: > : Given that GENERIC on -current doesn't support the 80386 anymore, it > : seems to me that we should probably be able to build releases with: > :=20 > : MACHINE_CPU=3D3Di386 i486 > :=20 > : If there's demand someone could create an 80386 release, but I suspect > : most people doing actual work on those are embeded system people who > : build their own worlds and thus are quite capable of setting MACHINE_CPU > : correctly. Obviously, we will have to ship 80386 compatable binaries > : for the entire life of the 4.x branch. >=20 > Your example is inconsistant with what you said. This example will > build i386 and i486 binaries. Setting MACHINE_CPU to "i386 i486" says that I will except i386 or i486 code in my binaries so there's a good chance they won't run on anything less the an i486. An actual 80386 would have to set MACHINE_CPU to "i386" because no other extension will actually work. Admittidly, this won't really help much with openssl since it appears to only have 586 and 686 assembly, but if there were 486 code, there's not reason I can see not to take advantage of that in the release builds since an 80386 won't boot from the CD anyway. In some ways, I think it would be nice to have a variable we could set to the actual CPU we are compiling to that would fill in MACHINE_CPU correctly. I suppose appropriate comments in /etc/defaults/make.conf would also be a reasionable substitute. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6lG9YXY6L6fI4GtQRAv6kAJ9XnmRL4iaJ4kOEGo1trC6E1qYRrQCfXGwn NqeIWZ0LAEddK22sgbzRAqM= =fH8i -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010221174601.A9511>