From owner-freebsd-questions Mon Oct 15 13: 1:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-82.dsl.lsan03.pacbell.net [64.165.226.82]) by hub.freebsd.org (Postfix) with ESMTP id D364037B40A for ; Mon, 15 Oct 2001 13:01:50 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3745B66B0E; Mon, 15 Oct 2001 13:01:50 -0700 (PDT) Date: Mon, 15 Oct 2001 13:01:50 -0700 From: Kris Kennaway To: "Gary W. Swearingen" Cc: Kris Kennaway , Erik Sabowski , freebsd-questions@FreeBSD.ORG Subject: Re: ports vs. packages Message-ID: <20011015130149.A6151@xor.obsecurity.org> References: <20011014173546.A1244@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from swear@blarg.net on Mon, Oct 15, 2001 at 08:27:17AM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 15, 2001 at 08:27:17AM -0700, Gary W. Swearingen wrote: > Kris Kennaway writes: >=20 > > If you want to enable optional settings in the port, you have no > > choice. If you insist on adding local CFLAGS customizations, you have > > no choice. Otherwise the only real benefit to using ports is the warm > > fuzzy you get from having compiled the software on your own machine. >=20 > I thought that another (small) benefit was that the programs would be > compiled for your Athlon or Pentium or 486 instead of for a 386. >=20 > Ports give that benefit without changing CFLAGS, right? IIRC, the only > thing the beginners docs (handbook?) suggested for CFLAGS is "-O -pipe". No, that will give you a port which is exactly the same as the package you could install, which is also built using those flags (those flags cause gcc to produce code which can run on anything from the lowliest 386 to the mightiest athlon or pentium 4). There might be some differences if the binary is statically linked, or if it detects optional software components on your system at compile-time, but if you want processor-specific optimizations you have to tell gcc to enable them. The canonical way to do this in FreeBSD is to use the CPUTYPE variable in /etc/make.conf. Kris --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7y0CtWry0BWjoQKURAnrqAJwKm7JYEh9wOgBL/Dez95oHLJyHbQCg3kDs WhRUd7aXcC29Q/nIcjVXmmE= =+n1D -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message