link failure (drivers/char/riscom8.c) (240test13p2)
Hi.
In the link phase of a kernel 240t13p2 build I get the following:
drivers/char/char.o: In function `tty_init':
drivers/char/char.o(.text.init+0x259): undefined reference to `riscom8_init'
I guess this is bacause riscom8_init is now a static function and thus tty_init cannot see it. If this is intentional or nat I cannot judge but I guess the fix is either to remove the static or the initcall from tty_init. The decision I leave with those who know what to do.
Signature · 8 lines
Regards,
Rasmus([email protected])
My other .sig is a porsche
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/Quoted 7 lines
drivers/char/char.o: In function `tty_init':
drivers/char/char.o(.text.init+0x259): undefined reference to `riscom8_init'I guess this is bacause
riscom8_initis now a static function and thustty_initcannot see it. If this is intentional or nat I cannot judge but I guess the fix is either to remove the static or the initcall fromtty_init. The decision I leave with those who know what to do.
Remove the call from tty_init. riscom8 now uses the new style initialisers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line · Alan Cox
Remove the call from
tty_init. riscom8 now uses the new style initialisers
I guess this would do it then.
drivers/char/tty_io.c +0 -3
@@ -2319,9 +2319,6 @@#ifdef CONFIG_DIGIEPCA pc_init ();#endif -#ifdef CONFIG_RISCOM8 -riscom8_init (); -#endif #ifdef CONFIG_SPECIALIX specialix_init ();#endif
Signature · 9 lines
Regards,
Rasmus([email protected])
Cutler Webster's Law: There are two sides to every argument, unless a
person is personally involved, in which case there is only one.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/