when i tried rsyslogd without any option from my board it will give following error.

rsyslog runtime error(-2066): could not load module '/home/vipul_test/lib/rsyslog/lmnet.so', dlopen: /home/vipul_test/lib/rsyslog/lmnet.so', dlopen: /home/vipul_test/lib/rsyslog/lmnet.so', dlopen: /home/vipul_test/lib/rsyslog/lmnet.so: cannot open shared object file: No such file or directory
[try http://www.rsyslog.com/e/2066 ]
Error during class init for object 'conf' - failing...
rsyslogd initializiation failed - global classes could not be initialized.
Did you do a "make install"?
Suggested action: run rsyslogd with -d -n options to see what exactly fails.
rsyslogd: run failed with error -2066 (see rsyslog.h or try http://www.rsyslog.com/e/2066 to learn what that number means)

while rsyslogd -d -n option is not running and giving segmentation fault as below.

Segmentation fault (core dumped)
ash Get The <Segmentation fault>, Retry!
Segmentation fault (core dumped)
ash Get The <Segmentation fault>, Retry Fail!

only rsyslogd -M /lib/rsyslogd option is running.

so how to run rsyslogd without any interpretation?

You're running Rsyslogd in a way that's not the default (as in: properly installed).
This means that you should be aware of the consequences of doing things "your way" and the ways how to fix those.
Running 'ldd' on the binary should show you where it expects to find its dependencies.
Adding directories to and exporting a customized LD_LIBRARY_PATH may help (or not).
So the best way would be to actually install the application properly.