Date: Fri, 16 Feb 2001 05:35:43 -0500 From: Jim Bloom <bloom@acm.org> To: Peter Jeremy <peter.jeremy@alcatel.com.au> Cc: Alfred Perlstein <bright@wintelcom.net>, Kris Kennaway <kris@obsecurity.org>, current@FreeBSD.ORG Subject: Re: OpenSSL ASM patch Message-ID: <3A8D027F.6F209D70@acm.org> References: <20010211094946.A51308@mollari.cthul.hu> <20010211122802.A78975@mollari.cthul.hu> <20010211124707.S3274@fw.wintelcom.net> <20010211125042.B79375@mollari.cthul.hu> <20010211130243.V3274@fw.wintelcom.net> <20010216155756.A70642@gsmx07.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I do plenty of build once and run on multiple machines. My biggest machine is a PII 40MHZ where I compile the world and kernels for a 486 laptop and P-60 Router/Firewall. I would not really want to compile the world on these slower machines over nfs. For my case, I guess I could rebuild only the ssl library for each machine properly tuned. For my small collection of machines, that wouldn't be too bad, but for larger sites it would be a problem. I could probably find some way to compile multiple version with buildworld and figure out the correct one to install with installworld. Jim Bloom bloom@acm.org Peter Jeremy wrote: > > IMHO, the main market for this feature would be people who just do > binary installs - if you're doing a buildworld, you can tune to your > hardware[1]. If we wanted to just speed up OpenSSL on binary > installs, we could have processor-optimised variants of libssl.* > available as packages (tick the box that suits your processor if you > want the optimised library). > > [1] I don't think there's a lot of `build once, install on lots of > different hardware', though I could be wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A8D027F.6F209D70>