Nope. A double slash in a path is ignored and treated as a single one. The error can be that it tries to copy all the files in perl... into perl itself. This is not possible in bash and indeed it is a non-sense. You have to investigate the reason why it put two slashes, anyway. Maybe it searches for a path or directory name stored in an environment variable and maybe that variable is undefined.
Suppose you have a command
cp -r /home/o2mars/perl/* /home/o2mars/$INSTALL_DIR/perl
if the environment variable INSTALL_DIR has not been previously assigned, the line of code above will be translated as the one reported by the error log. Just an idea.