Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

womm throws error on Ubuntu due to Perl #37

Open
buep opened this issue Aug 22, 2017 · 4 comments
Open

womm throws error on Ubuntu due to Perl #37

buep opened this issue Aug 22, 2017 · 4 comments

Comments

@buep
Copy link

buep commented Aug 22, 2017

$ ./womm 
Can't locate File/chdir.pm in @INC (you may need to install the File::chdir module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at ./womm line 8.
BEGIN failed--compilation aborted at ./womm line 8.

Ubuntu have Perl installed, but on Ubuntu 17.04 git is not default.

@lakruzz
Copy link
Owner

lakruzz commented Aug 22, 2017

Hmmm - it's line # 8 - but I'm not even using chdir anymore (did in one of the previous versions) I think you can just simply comment out or delete line 8.

...what happens then?

@buep

@buep buep changed the title womm throws error on Ubuntu womm throws error on Ubuntu due to Perl Aug 22, 2017
@buep
Copy link
Author

buep commented Aug 22, 2017

Then it can't find your module in modules

Can't locate modules/cmd.pm in @INC (you may need to install the modules::cmd module) (@INC contains: .. /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at ./womm line 23.
BEGIN failed--compilation aborted at ./womm line 23.

So it seems my machine resolve path different?

@buep
Copy link
Author

buep commented Aug 22, 2017

hmm, don't know a new playbook solves the problem.... did you mix up commits?

@lakruzz
Copy link
Owner

lakruzz commented Aug 22, 2017

YES!!! - sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants