#5019 closed defect (cant-reproduce)
make fails without pybabel
Reported by: | ayleph | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 0.8.0 |
Component: | infrastructure | Keywords: | make, babel |
Cc: | Christopher Allan Webber | Parent Tickets: |
Description
Trying to compile a fresh install of latest master results in an error if pybabel isn't installed on the system.
(mediagoblin-0.8.0) ~/mediagoblin-0.8.0 $ make ./devtools/compile_translations.sh ./devtools/compile_translations.sh: line 40: pybabel: command not found Makefile:118: recipe for target 'i18n' failed make: *** [i18n] Error 127
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Cc: | added |
---|
This is an interesting issue. setup.py
lists as a requirement Babel>=1.3
; however, make
calls setup.py
after i18n
, which wants to use pybabel
to build the translations. Can we change the order of operations in Makefile
?
comment:4 by , 10 years ago
Hm, so ./configure && make
should install ./bin/pybabel
, though it won't if you ran --without-virtualenv
, in which case it'll expect one to be on the $PATH
. Did you use --without-virtualenv
?
comment:5 by , 10 years ago
Okay my last comment was dumb, I didn't notice that you *did* say --without-virtualenv, but also had properly sourced your own virtualenv.
I'll give such a setup a try.
comment:6 by , 10 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Now that I think about it, this isn't surprising behavior. --without-virtualenv means that the system isn't setting up a virtualenv or etc for you, it's up to *you* to provide the dependencies. pybabel is such a dependency.
Maybe we can do something to improve warnings if --without-virtualenv is run so that it more stringently checks for system packages in the ./configure step, though I'm not entirely sure how to go about that.
comment:7 by , 7 years ago
This is very useful thanking you and appreciate your works, As we know to free eshop codes is use to play nintendo games.
To get around this, I executed the following command from within my virtualenv.
And in case it matters, I ran the fresh install as: