Hi, I was following a post on current when I changed to CPU_TYPE=p4... Also, I know how to get the CPU information from dmesg...The reason that I put p4 was accidental, it was cause I thought I had a PIV and didn't check...set it...basta... I do apologise for this mistake, and hope everyone will forgive me... Thanks, Anthony On Tuesday 29 April 2003 18:48, John Baldwin wrote: > On 29-Apr-2003 CARTER Anthony wrote: > > I DID compile with make.conf containing CPU_TYPE=p4... > > > > maybe an avenue...how do I fix without destroying everything? I AM on a > > PIII box (thought it was PIV). :( > > > > Thanks, a little wiser... > > Might I suggest that you run -stable for a while until you are a bit > more familiar with FreeBSD? The deprecation of DRM_LINUX was clearly > pointed out on the cvs-all_at_ when it happend, and people tracking > current really should be reading cvs-all_at_. Also, being able to > identify what CPU your system has from the dmesg is a rather basic > > task: > > dmesg | grep -A 2 ^CPU > > CPU: Intel Pentium III (696.97-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA, > CMOV,PAT,PSE36,MMX,FXSR,SSE> > > Finally, specifically with regards to CPUTYPE=p4, gcc is known to have > some problems with -march=p4 even on P4 machines as has been discussed > on current_at_ several times in the past few months. Following the threads > on current_at_ is a rather good idea when tracking -current much like > tracking cvs-all_at_.Received on Wed Apr 30 2003 - 05:31:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:05 UTC