Skip to contentSkip to conversation

2.5.52 compile error

DISCUSSION rtilley 6 participants 13 messages Dec 17, 2002 Char and misc drivers

lore
Share & tools
lore

rtilley

author
#0 lore raw

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to input_event' drivers/built-in.o(.text+0x18861): undefined reference to input_event' drivers/built-in.o: In function `kd_mksound':
drivers/built-in.o(.text+0x1890a): undefined reference to input_event' drivers/built-in.o: In function kbd_bh':
drivers/built-in.o(.text+0x197a2): undefined reference to input_event' drivers/built-in.o(.text+0x197c1): undefined reference to input_event' drivers/built-in.o(.text+0x197e0): more undefined references to `input_event' follow
drivers/built-in.o: In function `kbd_connect':
drivers/built-in.o(.text+0x19d54): undefined reference to input_open_device' drivers/built-in.o: In function kbd_disconnect':
drivers/built-in.o(.text+0x19d7f): undefined reference to input_close_device' drivers/built-in.o: In function kbd_init':
drivers/built-in.o(.init.text+0x12c1): undefined reference to `input_register_handler'
make: *** [.tmp_vmlinux1] Error 1

Where is the fix for this?

#1 lore raw
Quoted 24 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to input_event' drivers/built-in.o(.text+0x18861): undefined reference to input_event' drivers/built-in.o: In function `kd_mksound':
drivers/built-in.o(.text+0x1890a): undefined reference to input_event' drivers/built-in.o: In function kbd_bh':
drivers/built-in.o(.text+0x197a2): undefined reference to input_event' drivers/built-in.o(.text+0x197c1): undefined reference to input_event' drivers/built-in.o(.text+0x197e0): more undefined references to `input_event' follow
drivers/built-in.o: In function `kbd_connect':
drivers/built-in.o(.text+0x19d54): undefined reference to input_open_device' drivers/built-in.o: In function kbd_disconnect':
drivers/built-in.o(.text+0x19d7f): undefined reference to input_close_device' drivers/built-in.o: In function kbd_init':
drivers/built-in.o(.init.text+0x12c1): undefined reference to `input_register_handler'
make: *** [.tmp_vmlinux1] Error 1

Quoted 2 lines

Where is the fix for this?

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

Signature · 2 lines
Bob Miller					Email: [email protected]
Open Source Development Lab			Phone: 503.626.2455 Ext. 17
author
#2 lore raw

CONFIG_INPUT is modular, do I *have* to build it in inorder to compile?

Quoted 38 lines · Bob Miller
Quoted 24 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to input_event' drivers/built-in.o(.text+0x18861): undefined reference to input_event' drivers/built-in.o: In function `kd_mksound':
drivers/built-in.o(.text+0x1890a): undefined reference to input_event' drivers/built-in.o: In function kbd_bh':
drivers/built-in.o(.text+0x197a2): undefined reference to input_event' drivers/built-in.o(.text+0x197c1): undefined reference to input_event' drivers/built-in.o(.text+0x197e0): more undefined references to `input_event' follow
drivers/built-in.o: In function `kbd_connect':
drivers/built-in.o(.text+0x19d54): undefined reference to input_open_device' drivers/built-in.o: In function kbd_disconnect':
drivers/built-in.o(.text+0x19d7f): undefined reference to input_close_device' drivers/built-in.o: In function kbd_init':
drivers/built-in.o(.init.text+0x12c1): undefined reference to `input_register_handler'
make: *** [.tmp_vmlinux1] Error 1

Quoted 2 lines

Where is the fix for this?

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

Signature · 7 lines
Bob Miller					Email: [email protected]
Open Source Development Lab			Phone: 503.626.2455 Ext. 17
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#3 lore raw
In reply to Bob Miller
Quoted 7 lines · Bob Miller
Quoted 6 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to `input_event'

[more errors snipped]

Quoted 5 lines
Quoted 3 lines

Where is the fix for this?

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

And if you want to use your keyboard or mouse, something similar to the following may be helpful, depending on your system.

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y

Steven

author
#4 lore raw

Yes, my fingers need a keyboard. You are a very intelligent person to understand this. May your knowledge rub off onto me.

All of these options are modules in my config file, *must* they be built into the kernel in order to compile?

Quoted 29 lines · Steven Cole
Quoted 7 lines · Bob Miller
Quoted 6 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to `input_event'

[more errors snipped]

Quoted 5 lines
Quoted 3 lines

Where is the fix for this?

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

And if you want to use your keyboard or mouse, something similar to the following may be helpful, depending on your system.

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y

Steven

#5 lore raw
Quoted 3 lines

All of these options are modules in my config file, *must* they be built into the kernel in order to compile?

Yes!!! I have a patch for fixing this issue.

You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.

===================================================================

[email protected], 2002-12-10 12:07:45-08:00, jsimmons@kozmo.(none)
The VT tty layer depends on the input api now. Fixed this dependency.

 Kconfig |    1 +
 1 files changed, 1 insertion(+)
drivers/char/Kconfig +1 -0
diff -Nru a/drivers/char/Kconfig b/drivers/char/Kconfig
@@ -6,6 +6,7 @@
 
 config VT
 	bool "Virtual terminal"
+	depends on INPUT=y
 	---help---
 	  If you say Y here, you will get support for terminal devices with
 	  display and keyboard devices. These are called "virtual" because you

===================================================================

This BitKeeper patch contains the following changesets:
+
## Wrapped with gzip_uu ##

begin 664 bkpatch6044 M'XL(`+!+]CT``]54VVH;,1!]MKYB("\MQ;NZ[,T+6]RFEX24UKA.7TH?A';L MW=@KF97L9,-^?&6[N1!,H*5]J"X(9H;#F3D'G<"EQ38?7-FZ:8RVY3.C'7Y M8&EN&Q.\T$;C2Q^<&N.#X<:VH6U5N*KUYF98Z_7&$9^=2*<JV&)K\P$+Q'W$ M=6O,!]/W'R\_O9D24A1P6DF]P*_HH"B(,^U6KDH[EJY:&1VX5FK;H).!,DU_ M7]IS2KG?,4L%C9.>)31*>\5*QF3$L*0\RI*(W+4P?DS]"0KCC+)1%,6C7B24 M"?(.6)E&5>,G\H,)[3-(_B(<UR2N$H*+QB,*3D+?S=!DZ)@EF%\&T&SG6P MDAVV4.(:=6G!:'^MQ\YR'4-VEP'\*&^P=(G:ONK$+7JB7(.(TC<CD8>!D M^)N+$"HI>0VW]7J-J_%!\B;)EH%I%]_O6O_1EVV]4SY4E6S#"V7TO%X<ADT% MI9'@/.LYIUG6BU0D*.99R>>E$!R/3_<90_IWY1Y]40<97M'':O>F>O?T2:E MW.+56)D2/?DE=COD8+-\!I)Q?^/$JR[8B!]L)YZ:CHW^>]/M5?D"P_9Z?[R) L)D<%^@,SGF?R.`1L_//D\M9T3W\/ZI"M;2;IE!2\7B$2'X"W[RZ@MX$```` `
end

#8 lore raw
In reply to Bob Miller
Quoted 23 lines · Bob Miller
Quoted 21 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

drivers/built-in.o: In function `kd_nosound':
drivers/built-in.o(.text+0x1883f): undefined reference to input_event' drivers/built-in.o(.text+0x18861): undefined reference to input_event' drivers/built-in.o: In function `kd_mksound':
drivers/built-in.o(.text+0x1890a): undefined reference to input_event' drivers/built-in.o: In function kbd_bh':
drivers/built-in.o(.text+0x197a2): undefined reference to input_event' drivers/built-in.o(.text+0x197c1): undefined reference to input_event' drivers/built-in.o(.text+0x197e0): more undefined references to input_event' follow drivers/built-in.o: In function kbd_connect':
drivers/built-in.o(.text+0x19d54): undefined reference to input_open_device' drivers/built-in.o: In function kbd_disconnect':
drivers/built-in.o(.text+0x19d7f): undefined reference to input_close_device' drivers/built-in.o: In function kbd_init':
drivers/built-in.o(.init.text+0x12c1): undefined reference to `input_register_handler'
make: *** [.tmp_vmlinux1] Error 1

Quoted 5 lines
Quoted 2 lines

Where is the fix for this?

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

I did not know what is that mean (off the man page)?

Quoted 1 line

Is that at menuconfig
or
should modify any source code?

Signature · 3 lines
Sincere Eric
www.linuxspice.com
linux pc for sale
#9 lore raw
Quoted 7 lines · eric lin
Quoted 6 lines · Bob Miller
Quoted 4 lines · rtilley

Using RH's default *i686.config to build a vanilla 2.5.52 kernel. It keeps returning this error on 2 totally different x86 PCs:

Stuff deleted.

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines

Where is the fix for this?

Quoted 8 lines
Quoted 2 lines

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

I did not know what is that mean (off the man page)?

Quoted 1 line

Is that at menuconfig
or
should modify any source code?

Yes it is at off the first page of "make menuconfig".

Signature · 2 lines
Bob Miller					Email: [email protected]
Open Source Development Lab			Phone: 503.626.2455 Ext. 17
#6 lore raw
In reply to James Simmons
Quoted 32 lines · James Simmons
Quoted 2 lines

All of these options are modules in my config file, *must* they be built into the kernel in order to compile?

Yes!!! I have a patch for fixing this issue.

You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.

===================================================================

[email protected], 2002-12-10 12:07:45-08:00, jsimmons@kozmo.(none)
The VT tty layer depends on the input api now. Fixed this dependency.

 Kconfig |    1 +
 1 files changed, 1 insertion(+)

diff -Nru a/drivers/char/Kconfig b/drivers/char/Kconfig

drivers/char/Kconfig +1 -0
@@ -6,6 +6,7 @@
 
 config VT
 	bool "Virtual terminal"
+	depends on INPUT=y
 	---help---
 	  If you say Y here, you will get support for terminal devices with
 	  display and keyboard devices. These are called "virtual" because you
Quoted 4 lines

===================================================================

This BitKeeper patch contains the following changesets:

I copied this piece as patch1.tar.gz
--------------------------------------------------------------

Quoted 4 lines

+
## Wrapped with gzip_uu ##

Quoted 15 lines

begin 664 bkpatch6044 M'XL(`+!+]CT``]54VVH;,1!]MKYB("\MQ;NZ[,T+6]RFEX24UKA.7TH?A';L MW=@KF97L9,-^?&6[N1!,H*5]J"X(9H;#F3D'G<"EQ38?7-FZ:8RVY3.C'7Y M8&EN&Q.\T$;C2Q^<&N.#X<:VH6U5N*KUYF98Z_7&$9^=2*<JV&)K\P$+Q'W$ M=6O,!]/W'R\_O9D24A1P6DF]P*_HH"B(,^U6KDH[EJY:&1VX5FK;H).!,DU_ M7]IS2KG?,4L%C9.>)31*>\5*QF3$L*0\RI*(W+4P?DS]"0KCC+)1%,6C7B24 M"?(.6)E&5>,G\H,)[3-(_B(<UR2N$H*+QB,*3D+?S=!DZ)@EF%\&T&SG6P MDAVV4.(:=6G!:'^MQ\YR'4-VEP'\*&^P=(G:ONK$+7JB7(.(TC<CD8>!D M^)N+$"HI>0VW]7J-J_%!\B;)EH%I%]_O6O_1EVV]4SY4E6S#"V7TO%X<ADT% MI9'@/.LYIUG6BU0D*.99R>>E$!R/3_<90_IWY1Y]40<97M'':O>F>O?T2:E MW.+56)D2/?DE=COD8+-\!I)Q?^/$JR[8B!]L)YZ:CHW^>]/M5?D"P_9Z?[R) L)D<%^@,SGF?R.`1L_//D\M9T3W\/ZI"M;2;IE!2\7B$2'X"W[RZ@MX$```` `
end

-------------------------------------------------------------------
then in my /linux-2.5.52/

fsshl@www:~/linux-2.5.52$ gzip -cd patch1.tar.gz | patch -p1
patch: **** Only garbage was found in the patch input.

Please help

Quoted 8 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 3 lines
Sincere Eric
www.linuxspice.com
linux pc for sale
#7 lore raw
| > Yes!!! I have a patch for fixing this issue.
| >
| > You can import this changeset into BK by piping this whole message to:
| > '| bk receive [path to repository]' or apply the patch as usual.
| >
| > ===================================================================
| >
| >
| > [email protected], 2002-12-10 12:07:45-08:00, jsimmons@kozmo.(none)
| >   The VT tty layer depends on the input api now. Fixed this dependency.
| >
| >
| >  Kconfig |    1 +
| >  1 files changed, 1 insertion(+)
| >
| >
| > diff -Nru a/drivers/char/Kconfig b/drivers/char/Kconfig
| > --- a/drivers/char/Kconfig	Tue Dec 10 12:16:48 2002
| > +++ b/drivers/char/Kconfig	Tue Dec 10 12:16:48 2002
| > @@ -6,6 +6,7 @@
| >
| >  config VT
| >  	bool "Virtual terminal"
| > +	depends on INPUT=y
| >  	---help---
| >  	  If you say Y here, you will get support for terminal devices with
| >  	  display and keyboard devices. These are called "virtual" because you
| >
| > ===================================================================
| >
| >
| > This BitKeeper patch contains the following changesets:
| I copied this piece as patch1.tar.gz

This piece is just the above piece in gz format. You don't need this latter piece, just the above part.

| --------------------------------------------------------------
| > +
| > ## Wrapped with gzip_uu ##
| >
| >
| > begin 664 bkpatch6044
| > M'XL(`+!+]CT``]54VVH;,1!]MKYB("\MQ;NZ[,T+6]RFEX24UKA.7TH?A';L
| > MW=@KF97L9,-^?&6[N1!,H*5]J"X(9H;#F3D'G<"EQ38?7-FZ:8RVY`3.C'7Y
| > M8&EN&Q.\T$;C2Q^<&N.#X<:VH6U5N*KUYF98Z_7&$9^=2*<JV&)K\P$+Q'W$
| > M=6O,!]/W'R\_O9D24A1P6DF]P*_HH"B(,^U6KDH[EJY:&1VX5FK;H).!,DU_
| > M7]IS2KG?,4L%C9.>)31*>\5*QF3$L*0\RI*(W+4P?DS]"0KCC+)1%,6C7B24
| > M"?(.6)`E&5`>,G\H,)[3-(_B(<UR2N$H*+QB,*3D+?S=!DZ)@EF%\&T&SG6P
| > MDAVV4.(:=6G!:'`^MQ\YR'4-VEP'\*&^P=(G:ONK$+7J`B`7(.(TC<CD8>!D
| > M^)N+$"HI>0VW]7J-J_%!\B;)EH%I%]_O6O_1EVV]4SY4E6S#"V7TO%X<ADT%
| > MI9'@/.LYIUG6BU0D*.99R>>E$!R/3_<90`_IWY1Y]40<97M'':O>F>O?T2:E
| > MW.+56)D2/?DE=COD8+-\!I)Q?^/$JR[8B!]L)YZ:CHW^>]/M5?D"P_9Z?[R)
| > L)D<%^@,SGF?`R.`1L_//D\M9T3W\/ZI"M;2;IE!2\7B$2'X"W[RZ@MX$````
| > `
| > end
| >
| -------------------------------------------------------------------
| then in my /linux-2.5.52/
|
| fsshl@www:~/linux-2.5.52$ gzip -cd patch1.tar.gz | patch -p1
| patch: **** Only garbage was found in the patch input.

Yep.

| Please help

Signature · 1 line
~Randy
#10 lore raw
In reply to Bob Miller

in the Input device suppoort
I did not see Config_inout in make menuconfig, so I suppose is first item(if I am wrong please notify me)

them make dep, meke clean, make modules
then it terminate some other error

gcc -Wp,-MD,fs/intermezzo/.inode.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=inode -DKBUILD_MODNAME=intermezzo -c -o fs/intermezzo/inode.o fs/intermezzo/inode.c
make[2]: *** No rule to make target fs/intermezzo/io_daemon.s', needed by fs/intermezzo/io_daemon.o'. Stop. make[1]: *** [fs/intermezzo] Error 2
make: *** [fs] Error 2

please help

Quoted 12 lines
Quoted 9 lines
Quoted 2 lines

At your finger tips ;-). Turn on CONFIG_INPUT via "Input device support" off the main page.

I did not know what is that mean (off the man page)?

Is that at menuconfig
or
should modify any source code?

Yes it is at off the first page of "make menuconfig".

Signature · 3 lines
Sincere Eric
www.linuxspice.com
linux pc for sale
#11 lore raw

On Wed, 18 Dec 2002, eric lin wrote:

| in the Input device suppoort
| I did not see Config_inout in make menuconfig, so I suppose is first
| item(if I am wrong please notify me)

It's "Input device support", immediately after Telephony Support and just before Character devices.

| them make dep, meke clean, make modules
| then it terminate some other error
|
|   gcc -Wp,-MD,fs/intermezzo/.inode.o.d -D__KERNEL__ -Iinclude -Wall
| -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
| -pipe -mpreferred-stack-boundary=2 -march=i686 -Iarch/i386/mach-generic
| -fomit-frame-pointer -nostdinc -iwithprefix include -DMODULE
| -DKBUILD_BASENAME=inode -DKBUILD_MODNAME=intermezzo   -c -o
| fs/intermezzo/inode.o fs/intermezzo/inode.c
| make[2]: *** No rule to make target `fs/intermezzo/io_daemon.s', needed
| by `fs/intermezzo/io_daemon.o'.  Stop.
| make[1]: *** [fs/intermezzo] Error 2
| make: *** [fs] Error 2

Just remove io_daemon.o from the fs/intermezzo/Makefile .

Signature · 1 line
~Randy
#12 lore raw
Quoted 5 lines

Just remove io_daemon.o from the fs/intermezzo/Makefile .

Thanks your point out, it pass this problem at compile time, then it still terminate by another error

gcc -Wp,-MD,drivers/block/.ps2esdi.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=ps2esdi -DKBUILD_MODNAME=ps2esdi -c -o drivers/block/ps2esdi.o drivers/block/ps2esdi.c
drivers/block/ps2esdi.c:185: redefinition of `__initfn'
drivers/block/ps2esdi.c:171: `__initfn' previously defined here
drivers/block/ps2esdi.c: In function `__initfn':
drivers/block/ps2esdi.c:189: warning: initialization from incompatible pointer type drivers/block/ps2esdi.c:192: dereferencing pointer to incomplete type drivers/block/ps2esdi.c:192: dereferencing pointer to incomplete type drivers/block/ps2esdi.c:193: dereferencing pointer to incomplete type drivers/block/ps2esdi.c:196: dereferencing pointer to incomplete type drivers/block/ps2esdi.c:197: dereferencing pointer to incomplete type drivers/block/ps2esdi.c:199: dereferencing pointer to incomplete type drivers/block/ps2esdi.c: In function `__exitfn':
drivers/block/ps2esdi.c:207: warning: implicit declaration of function mca_mark_as_unused' drivers/block/ps2esdi.c:215: i' undeclared (first use in this function) drivers/block/ps2esdi.c:215: (Each undeclared identifier is reported only once drivers/block/ps2esdi.c:215: for each function it appears in.)
drivers/block/ps2esdi.c: In function `ps2esdi_geninit':
drivers/block/ps2esdi.c:298: warning: implicit declaration of function mca_find_adapter' drivers/block/ps2esdi.c:298: MCA_NOTFOUND' undeclared (first use in this function) drivers/block/ps2esdi.c:309: warning: implicit declaration of function mca_set_adapter_name' drivers/block/ps2esdi.c:315: warning: implicit declaration of function mca_mark_as_used' drivers/block/ps2esdi.c:316: warning: passing arg 2 of mca_set_adapter_procfn' from incompatible pointer type drivers/block/ps2esdi.c:333: warning: implicit declaration of function mca_read_stored_pos' drivers/block/ps2esdi.c: In function `do_ps2esdi_request':
drivers/block/ps2esdi.c:508: warning: long long unsigned int format, different type arg (arg 3) {standard input}: Assembler messages:
{standard input}:216: Error: symbol `__initfn' is already defined
make[2]: *** [drivers/block/ps2esdi.o] Error 1
make[1]: *** [drivers/block] Error 2
make: *** [drivers] Error 2

highly appreciate any advancer's advice

Signature · 3 lines
Sincere Eric
www.linuxspice.com
linux pc for sale