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

whipper fails to build on bash-compgen #25

Closed
RecursiveForest opened this issue Jul 22, 2016 · 4 comments
Closed

whipper fails to build on bash-compgen #25

RecursiveForest opened this issue Jul 22, 2016 · 4 comments
Labels
Bug Generic bug: can be used together with more specific labels

Comments

@RecursiveForest
Copy link
Contributor

RecursiveForest commented Jul 22, 2016

make[2]: Entering directory '/home/samantha/prj/whipper-build/etc/bash_completion.d'
PYTHONPATH=../..:$PYTHONPATH ./bash-compgen \
    rip morituri.rip.main.Rip > rip
  File "./bash-compgen", line 178
    exec command
               ^
SyntaxError: Missing parentheses in call to 'exec'`

I have run through the git submodule init, git submodule update ./autogen.sh and ./configure as specified in the README.

@RecursiveForest
Copy link
Contributor Author

It seems as if all that autogen crap isn't sufficient to figure out whether my system is using python2 or python3 as python, so you have to force PYTHON=$(which python2) (pulled this from the AUR PKGBUILD). I'll be updating the README.

@RecursiveForest
Copy link
Contributor Author

RecursiveForest@4617fe1 has a fix

@RecursiveForest
Copy link
Contributor Author

0001-update-README-to-force-python2.txt

Github is a bit retarded and I can't do two critical things:

  1. Fork this repository, since my 'morituri' repo is part of the same 'family'
  2. Upload a .patch I have created with git format-patch. So I had to change the extension to .txt for you; just change it back and run git am on it.

If anyone can tell me how to register my second repo (whipper) as part of this family of repos, please let me know.

@JoeLametta JoeLametta added the Bug Generic bug: can be used together with more specific labels label Jul 23, 2016
@JoeLametta
Copy link
Collaborator

JoeLametta commented Jul 23, 2016

Merged.
I don't have an answer to your question but I've just added you as collaborator so, if you confirm, you'll get push access to this repository (this way, instead of forking, you can create and work on branches).

PS: Thanks for reporting this issue and providing a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Generic bug: can be used together with more specific labels
Projects
None yet
Development

No branches or pull requests

2 participants