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

syntax error in VERSION script #45

Open
kyrias opened this issue Jun 15, 2017 · 2 comments
Open

syntax error in VERSION script #45

kyrias opened this issue Jun 15, 2017 · 2 comments

Comments

@kyrias
Copy link

kyrias commented Jun 15, 2017

Getting the following error when trying to build the python bindings using python 3.6:

/usr/bin/ld:bindings/python/.libs/macaroons.ver:2: syntax error in VERSION script

Said file contains the following:

{ global:
local: *; };

Same issue as #16 that was closed without actually being addressed.

@rescrv
Copy link
Owner

rescrv commented Jun 15, 2017

It's been awhile since I saw this issue, so please forgive me if this doesn't fix things right away.

The root cause here is that the macaroons.ver file is generated early on and systems with both Python3 and Python2 don't play nice. I believe that you can solve this by completely cleaning the repository (I use git clean -xfd, which can/will destroy all files in the working directory that are not checked in) and then rebuilding with autoreconf -ivf && ./configure PYTHON=/path/to/chosen/python.

I believe Evan closed #16 because he found some joy in implementing PyMacaroons and it fixed his issue.

@rescrv
Copy link
Owner

rescrv commented Jun 16, 2017

I've taken another look at this now, and it looks like the problem comes down to how you build and use the python module. As of the commit I just pushed to github (I forgot to push awhile back... whooops), I can do:

  • git clean -xfd && autoreconf -ivf && ./configure PYTHON=/usr/bin/python2 && make && make check
  • git clean -xfd && autoreconf -ivf && ./configure PYTHON=/usr/bin/python3 && make && make check

I think this demonstrates a viable solution. If you could confirm, I would appreciate it. I'll leave the issue open a week or more longer, and if I don't hear anything I'll close it. If I do that, please reopen it with more information and we can work to resolve the problem. I am able to create the same problem you describe with older commits before the 2/3 bilingual-ness was added (9cc2f68).

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