Re: make.conf file CPUTYPE?
On 12/25/04 20:58:12, Kris Kennaway wrote: On Sat, Dec 25, 2004 at 08:17:00PM -0500, Gerard Seibert wrote: When I ran 'buildkernel' as well as 'buildworld', I used the 'CPUTYPE?=i686' directive in the 'make.conf' file. I was wondering if it is correct to leave it in the 'make.conf' file now that I am finished building a new kernel and updating the system. Would I be better off if I just removed it, or changed it to 'CPUTYPE=i686'. I assumed that the '?' was just for the 'buildworld' procedure. Setting it with ?= was a bug that was recently fixed. You can cvsup and continue to set it with =. Kris What happened to march= in make.conf. Has it been depreciated? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf file CPUTYPE?
On Tue, Dec 28, 2004 at 06:18:39AM +, jason henson wrote: On 12/25/04 20:58:12, Kris Kennaway wrote: On Sat, Dec 25, 2004 at 08:17:00PM -0500, Gerard Seibert wrote: When I ran 'buildkernel' as well as 'buildworld', I used the 'CPUTYPE?=i686' directive in the 'make.conf' file. I was wondering if it is correct to leave it in the 'make.conf' file now that I am finished building a new kernel and updating the system. Would I be better off if I just removed it, or changed it to 'CPUTYPE=i686'. I assumed that the '?' was just for the 'buildworld' procedure. Setting it with ?= was a bug that was recently fixed. You can cvsup and continue to set it with =. Kris What happened to march= in make.conf. Has it been depreciated? Not as such, but CPUTYPE does it better (because it also enables cpu-specific asm code in some places, and you don't have to remember gcc syntax). Kris pgpaMMCNNeeOh.pgp Description: PGP signature
make.conf file CPUTYPE?
When I ran 'buildkernel' as well as 'buildworld', I used the 'CPUTYPE?=i686' directive in the 'make.conf' file. I was wondering if it is correct to leave it in the 'make.conf' file now that I am finished building a new kernel and updating the system. Would I be better off if I just removed it, or changed it to 'CPUTYPE=i686'. I assumed that the '?' was just for the 'buildworld' procedure. Thanks in advance. Gerard Seibert [EMAIL PROTECTED] My formula for success is rise early, work late, and strike oil. -- J. Paul Getty ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf file CPUTYPE?
On Sat, Dec 25, 2004 at 08:17:00PM -0500, Gerard Seibert wrote: When I ran 'buildkernel' as well as 'buildworld', I used the 'CPUTYPE?=i686' directive in the 'make.conf' file. I was wondering if it is correct to leave it in the 'make.conf' file now that I am finished building a new kernel and updating the system. Would I be better off if I just removed it, or changed it to 'CPUTYPE=i686'. I assumed that the '?' was just for the 'buildworld' procedure. Setting it with ?= was a bug that was recently fixed. You can cvsup and continue to set it with =. Kris pgpGSxV3FFGdQ.pgp Description: PGP signature
RE: make.conf file CPUTYPE?
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Gerard Seibert Sent: Sunday, December 26, 2004 6:47 To: freebsd-questions Subject: make.conf file CPUTYPE? When I ran 'buildkernel' as well as 'buildworld', I used the 'CPUTYPE?=i686' directive in the 'make.conf' file. I was wondering if it is correct to leave it in the 'make.conf' file now that I am finished building a new kernel and updating the system. Would I be better off if I just removed it, or changed it to 'CPUTYPE=i686'. I assumed that the '?' was just for the 'buildworld' procedure. snip The ? is required onlyif you build a kernel for one architecture on a different architecture. For example, you try to build a kernel for a P1 on a P4 box. You would be better of with CPUTYPE=i686 or more precisely something like CPUTYPE=p3 (in case you are building the world/kernel) for a Pentium III system. And I wuld recommend to leave the same in make.conf even after completion of the building because, all subsequent builds would be optimized for the processor mentioned in CPUTYPE Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
