Building packages for a variety of systems

Matthew Seaman matthew at
Mon Apr 20 18:21:26 UTC 2020

On 20/04/2020 18:15, Bob Healey wrote:
> I would like to move from building ports with my custom options on each
> system, and move to building once in a central location, and then
> deploying via pkg add.  Mainly openldap, samba, BIND, and their
> dependencies.  Do I need to use my oldest CPU (Opteron 1000 series) as
> the build host, or can I get away with using something much newer (Xeon
> E5-2000 v3) with more cores and RAM?  I'm seeing mixed opinions about
> ports hard coding build CPU features into binaries, and don't want to
> get stuck.

So long as you don't specify a particular CPU type in your compilation
flags -- ie. leave the flags at their default settings -- then it should
be absolutely fine to build on any amd64-compatible machine to deploy on
practically any other amd64-compatible machine.  Compilers on FreeBSD
are configured to support a generic CPU which all more recent designs
than the Intel 486 or 586 should be backwardly compatible with.

After all, the cerntral FreeBSD package build servers are pretty highly
specified rack-mount servers, but the packages built on them are
expected to work on much older and less capable hardware.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the freebsd-questions mailing list