>> > Sounds like maybe something involved with make(1) itself got
>> > corrupted. Rare, but it happens. Reinstalling the base system
>> > would probably help (just do a "binary upgrade" -- you don't need
>> > to reinstall the whole system).
>> >
>> Really?! I'll _gladly_ give that a shot and see
Hello,
> "/dev/null" <[EMAIL PROTECTED]> writes:
>
>> Hello,
>> Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
>> showed up. Installed the CPU drafted a new config for the kernel cd'd to
>> /usr/src, typed "make buildkernel KERNCONF=DEMON01", build process went
>> as
>> exp
On Thu, Apr 28, 2005 at 08:31:02AM -0400, Lowell Gilbert wrote:
> "/dev/null" <[EMAIL PROTECTED]> writes:
>
> > Hello,
> > Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
> > showed up. Installed the CPU drafted a new config for the kernel cd'd to
> > /usr/src, typed "make
"/dev/null" <[EMAIL PROTECTED]> writes:
> Hello,
> Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
> showed up. Installed the CPU drafted a new config for the kernel cd'd to
> /usr/src, typed "make buildkernel KERNCONF=DEMON01", build process went as
> expected. But before
