1 |
On 22 Mar 2008, at 01:08, Neil Bothwick wrote: |
2 |
> On Fri, 21 Mar 2008 21:23:11 +0000, Stroller wrote: |
3 |
> |
4 |
>> I suspect that this is caused because CONFIG_SCSI_WAIT_SCAN depends |
5 |
>> upon some other kernel option, and because you have that compiled in |
6 |
>> as a module. Thus the dependencies of the "parent" are forced to be |
7 |
>> modular. |
8 |
> |
9 |
> I thought Dale said that he hadn't anything set to compile as a |
10 |
> module. |
11 |
|
12 |
He doesn't seem to specifically state that. |
13 |
He does (subsequently?) say that he doesn't _want_ anything as a |
14 |
module (beware teh dark side!), but that's not the same thing. |
15 |
|
16 |
As I read Dale's original post, all he says is "I set |
17 |
CONFIG_SCSI_WAIT_SCAN as `not set`" (and in his post of 21 March 2008 |
18 |
16:13:49 GMT he says "if I say `compile it in'") "and it keeps |
19 |
turning back into a module". |
20 |
|
21 |
Of course this would prolly be much easier if Dale just posted a copy |
22 |
of his .config. I have a feeling something "obvious" is being |
23 |
overlooked, and it wouldn't do any hard to post the output of `cd / |
24 |
usr/src/linux && ls -ld /usr/src/linux && md5sum .config && make && |
25 |
make modules_install` so we can see stuff for ourselves. You'll |
26 |
notice that I look to check things like the /usr/src/linux symlink |
27 |
here and that the .config used is actually the same one as I suggest |
28 |
he posts. |
29 |
|
30 |
Stroller. |
31 |
-- |
32 |
gentoo-user@l.g.o mailing list |