[SOLVED] building dependencies for kernel modules in cross compiling environment

I tried to execute depmod.pl with the following command:
$ depmod.pl \
> -k ./vmlinux -F ./System.map \
> -b ${PRJROOT}/images/modules-2.6.20/lib/modules > \
> ${PRJROOT}/images/modules-2.6.20/lib/modules/2.6.20/modules.dep

However the file path is different in my execution environment and it is valid for sure. The file path here i mean to say are for the files vmlinux, System.map , modules.dep and the folder path for modules are in a different location in my executing environment than this but i gave it correctly for sure.

it is giving error message as follows:
"depmod.pl : command not found" even though executable for perl is available and it's path was aleady added in the PATH ( /usr/bin/perl )env variable.
I have checked that the depmod.pl is made as executable in the file's properties.

I am trying this for cross compiled output files vmlinux and System.map and the depmod.pl file is taken from busybox 1.22.1 located in examples folder of busy box source.

Please let me know the reason why it is not building dependencies in modules.dep file.

The error message is pretty clear. You didn't give a full path to depmod.pl and it did not find it in your PATH. The error message never mentioned Perl.

Originally Posted by smallpond The error message is pretty clear. You didn't give a full path to depmod.pl and it did not find it in your PATH. The error message never mentioned Perl.

No before executing that command(depmod.pl) i have changed the current working directory using cd(change directory) command to the one where depmod.pl file located.

The current directory is not in your PATH. There are explanations of why in any UNIX manual. You can include the path using ./depmod.pl

Originally Posted by smallpond The current directory is not in your PATH. There are explanations of why in any UNIX manual. You can include the path using ./depmod.pl

Hi, by prepending./ the command got executed. And I like to share one experience that when using both -k and -F options it didnot work mentioning that only any one of the kernel image(-k option) or System.map (-F option) should be used and not the both at same time. Then removing one of the options it worked. And after that while execution of the command in terminal output i was seeing messages like unresolved symbols for many items. Also when opened modules.dep file there are few rows where there are some .ko files listed corresponding to a .ko file after the ':' character and some doesnot having any .ko files after that ':' character and remains empty. Do these are warnings that at runtime it will cause problem like the symbols are not resolved or not able to link to the required files, so and so? please reply.