Unresolved symbols (NOT A BUG)
hi,
i try to add syslog support into net/ipv4/netfilter/ipt_LOG.c . so i added an include to sys/syslog.h and used the functions in there.
i now get unresolved symbols for each function i use from syslog.h .
my question is, must i merge the whole syslog code to the kernel for being able to use syslog in the above mentioned mod?
i added a 'firewall' facility to syslog and want all netfilter logs coming throuh ipt_LOG log to this facility.
sorry if this sounds 'strange', but i'm relative new to the kernel sources.
i started this cause i have not seen a possibility to log to a specific facility with the klog daemon.
bye,
sascha
You know you could try to use ULOGD target. It's easier to hack that than the kernel.
bye
Quoted 30 lines · Sascha Andres
hi,
i try to add syslog support into
net/ipv4/netfilter/ipt_LOG.c. so i added an include tosys/syslog.hand used the functions in there.i now get unresolved symbols for each function i use from
syslog.h.my question is, must i merge the whole syslog code to the kernel for being able to use syslog in the above mentioned mod?
i added a 'firewall' facility to syslog and want all netfilter logs coming throuh
ipt_LOGlog to this facility.sorry if this sounds 'strange', but i'm relative new to the kernel sources.
i started this cause i have not seen a possibility to log to a specific facility with the klog daemon.
bye,
sascha
-
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/
hi,
Quoted 3 lines
You know you could try to use ULOGD target. It's easier to hack that than
the kernel.
as far as I can see the patch simply adds code to the kernel. perhaps I did not get the point. why it's easier?
for me as a beginner it's just the same prob. hacking it would lead to unresolved symbols.
would it help to place syslog.h in linux include dir?
ciao sascha