quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---

quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---

quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---

quote:

---

> Building a kernel (2.4.22) does not work:
>
> I get the following message:
>
> driver/input/inputdrv.o(.text+0x845): In function 'emulate_raw':
> :undefined reference to 'handle_scancode'
>
> and a few more like them.
>
> also:
>
> driver/input/inputdrv.o(.text+0x845): In function 'keybdev_event':
> :undefined reference to 'keyboard_tasklet'
>
> I feel it must have something to do with my coices in 'make
> menuconfig', because earlier I succeeded in running the 'make' to a
> proper end...
>
>
> but which setting in menuconfig ?
>
> and:
>
> how could I protect myself against these wrong (combination of)
> choices ?
>
>
> frgr
> Erik

---

quote:

---

>
>Before starting anything in building your own kernel, directly after
>unpacking the source, run a:
>
>make mrproper
>
>This is highly needed.
>
>Alexander

---

quote:

---

>
>
>
> but I did !! I really really did....
>
> :-(
>
>
> and another thing: using my 2.4.22 .config on 2.4.20 (original RH)
> produced the same result.
> No strange things happened in make dep...
>
> It must be two incompatible settings or so...
>
> What I did was:
> run make menuconfig on the 2.4.22 kernel and save the settings as
> erik_config.
> then exiting make menuconfig while saving (as .config , no doubt).
>
> then make dep and make bzImage
>
> then copy erik_config to the 2.4.20 directory as .config.
> run make dep and make bzImage on the 2.4.20 kernel.
>
>
> frgr
> Erik

---

quote:

---

> e®ik <et57__DELETE__THIS__@hotmail.com> wrote:

---

quote:

---

[QUOTE][color=darkred]
> This can't work! Or just in a few configuration cases. Don't do such
> funny things, no wonder for the errors. Go and run a correct menuconfig
> on the older kernel and not by using a .config file from a newer one.

---