From: Scott Bronson <bronson@rinspin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: smp_num_cpus undeclared workaround
Date: 14 Aug 2002 17:25:39 -0700 [thread overview]
Message-ID: <1029371140.20412.29.camel@emma> (raw)
In-Reply-To: <1029367539.20388.7.camel@emma>
Dammit, I'm sorry about this...
Everything here is true, but this message is incomplete. I wanted to do
some more research before posting this so I told Evolution to "Send
Later."
Apparently, to Evolution, Send Later means Send in About 15 Minutes.
I'll post again after I've played around some more. Again, my
apologies.
On Wed, 2002-08-14 at 17:15, Scott Bronson wrote:
> Kernel 2.4.19:
>
> I was being plagued by the smp_num_cpus undeclared problems that seems
> be circulating since the 2.3 days. I appear to have triggered it by
> turning SMP on, doing a full build, and then turning it off. No
> combination of make clean/dep/etc fixes it. Finally, in desperation, I
> tried:
>
> cp .config ~/config.bak
> make mrproper
> cp ~/config.bak .config
> make
>
> And that fixed it. Surprising. Has anyone looked into what file
> isn't being properly cleaned? Given the LKML traffic that this
> problem has generated, this should probably be fixed.
>
>
> Thanks,
>
> - Scott
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-08-15 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 0:15 smp_num_cpus undeclared workaround Scott Bronson
2002-08-15 0:25 ` Scott Bronson [this message]
2002-08-15 0:55 ` Rik van Riel
2002-08-15 3:35 ` Scott Bronson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029371140.20412.29.camel@emma \
--to=bronson@rinspin.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox