Use -fno-stack-protector when building kernel modules. The vanilla kernel has its own overflow detection, and adding ssp on top doesn't seem to offer any advantage, so the kernel and modules should be built without ssp.
robert On March 1, 2006 02:28 pm, Warren Wilder wrote: > I'm trying to compile lirc: Linux Infrared Remote Control > > I know this list is not really meant to answer any and all software > problems, but the lirc mailling list isn't very responsive. I've only had a > few replies from users; mentioning that they ran into the same problem and > opted for no longer using a hardened system, changing their kernel, or > whatever. I'm hoping there is a real solution. > > I'm basically asking for a theoretical answer, but anyone with actual hands > on lirc compiling experience is of course very welcome with their advice. > When compiling the module which communicates with /dev/ttyS0, these > warnings fly by: > > *** Warning: "lirc_unregister_plugin" > [/usr/src/lirc/lirc-0.8.0/drivers/lirc_serial/lirc_serial.ko] undefined! > *** Warning: "lirc_register_plugin" > [/usr/src/lirc/lirc-0.8.0/drivers/lirc_serial/lirc_serial.ko] undefined! > *** Warning: "__guard" > [/usr/src/lirc/lirc-0.8.0/drivers/lirc_serial/lirc_serial.ko] undefined! > *** Warning: "__stack_smash_handler" > [/usr/src/lirc/lirc-0.8.0/drivers/lirc_serial/lirc_serial.ko] undefined! > > After the compilation, running modprobe lirc_serial reveals pretty much the > same messages, but without the warning part. > I'm not much of a programmer, so I'm not sure what this program is doing > differently. Somehow it is not using libc? It is linking against my kernel > source though. > > Warren > > _________________________________________________________________ > On the road to retirement? Check out MSN Life Events for advice on how to > get there! http://lifeevents.msn.com/category.aspx?cid=Retirement -- http://linuxfromscratch.org/mailman/listinfo/hlfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
