-
Notifications
You must be signed in to change notification settings - Fork 17
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
Trouble to compile geanypy in Debian-Wheezya and Squeeze #6
Comments
I guess that says something like "no rule to make target Can you try to do this:
I recently made some build system changes and it might just need to be cleaned up in your working directory and rebuilt/generated from scratch. |
Thanks for your answer, but no work |
Do you mind trying to re-checkout from Git again into a new directory and then build from scratch? |
@cristianchaparroa what's the problem you actually have? Your paste seems just fine to me if my Make and online-translator skills don't fool me. BTW, you seem to be building as root (since the directory is FTR, the paste translated to English:
|
geanypy try to compile in debian squeeze and wheezy and it generates the same error:
....
CC geanypy_la-geanypy-signalmanager.lo
CC geanypy_la-geanypy-templates.lo
CC geanypy_la-geanypy-uiutils.lo
CCLD geanypy.la
make[2]: se sale del directorio
/root/src/geanypy/src' make[1]: se sale del directorio
/root/src/geanypy/src'Making all in geany
make[1]: se ingresa al directorio
/root/src/geanypy/geany' GEN __init__.pyc GEN console.pyc GEN manager.pyc GEN loader.pyc GEN plugin.pyc GEN signalmanager.pyc make[1]: se sale del directorio
/root/src/geanypy/geany'Making all in plugins
make[1]: se ingresa al directorio
/root/src/geanypy/plugins' make[1]: No se hace nada para
all'.make[1]: se sale del directorio
/root/src/geanypy/plugins' make[1]: se ingresa al directorio
/root/src/geanypy'make[1]: No se hace nada para
all-am'. make[1]: se sale del directorio
/root/src/geanypy'I have followed the instructions of the official documentation and does not work.
May be due to this error and how can fix it?
The text was updated successfully, but these errors were encountered: