Date: Sun, 26 Dec 2004 08:16:01 +0530 From: "Subhro" <subhro.kar@gmail.com> To: "'Gerard Seibert'" <gerard-seibert@rcn.com>, "'freebsd-questions'" <freebsd-questions@freebsd.org> Subject: RE: make.conf file & CPUTYPE? Message-ID: <41ce25f2.2482264c.5bba.14d7@smtp.gmail.com> In-Reply-To: <Pine.WNT.4.61.0412252006250.3864@Treneq>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
> -----Original Message-----
> From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-
> questions@freebsd.org] 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
[-- Attachment #2 --]
0 *H
010 + 0 *H
0=0 ͺVT"rU0
*H
0_10 UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0
960129000000Z
280801235959Z0_10 UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00
*H
0 mVa-Hqg뷞
8%Fs$]
enVsߴX9knը?144g NEVixG)6c\-{2{0*/1g 0
*H
L?hC3]Mz36ؕ"6hl|B.?OvJ͠
)"]݁#{%F0yK@<_SH䆴{5{%ӎ?8 4 q0f0Ϡ
O[uj)0
*H
0_10 UUS10U
VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0
980512000000Z
080512235959Z010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00
*H
0 ZDUz-Ox6
JoTw*h1ApzKHV-BD\B/;'
]6B3nTOJƚj$e~7jJ 00 `HB05U.0,0*(&$http://crl.verisign.com/pca1.1.1.crl0GU @0>0<`HE0-0++www.verisign.com/repository/RPA0U0 0U0
*H
B|ߌyLMU/P^N.^2yeJRը1!l4x BZъު"!e3 3
>5d$[h|7d
Ž33>>s020:N4fr40
*H
010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0
041111000000Z
050718235959Z010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10U
Subhro Kar1#0! *H
subhro.kar@gmail.com00
*H
0 )Fp["
,9Uڵ87(v0r1C.\4VP@h!"r(
⎅?-"2K 00 U0 0DU =0;09`HE0*0(+https://www.verisign.com/rpa0U0U%0++0
`HENone03U,0*0(&$"http://crl.verisign.com/class1.crl0
*H
]5羧n-A$NyiIk{}Y(DKTHE@&mZK#TEWO.bqƼsE $raEsh{Os{[=zz_,v߈QԊ>1>0:0010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated:N4fr40 + 0 *H
1 *H
0 *H
1
041226024601Z0# *H
1@v_ +|:Jk0g *H
1Z0X0
*H
0*H
0
*H
@0+0
*H
(0+0
*H
0 +710010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated:N4fr40*H
1䠁010U
VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated:N4fr40
*H
m0
ݷ& K2ChByMfoׯj*yXFH% ,%4CNWޖRmW؍ʄ|8nK{1Bݿ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41ce25f2.2482264c.5bba.14d7>
