Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
error: [Errno 2] No such file or directory: 'build/test1.c' #22
Comments
|
It looks like a permissions issue to me. The setup script is trying to create a "build" directory but doesn't have permission to do so. Running the setup with elevated privileges should remedy the issue. |
juanrubio
commented
Jul 7, 2016
|
I've tried running snapcraft with sudo, with the same effect. There is the possibility that this is a snapcraft defect. I also raised a ticket in launchpad: |
|
This may be a shot in the dark but what version comes up when you type "python --version"? Looking over the setup script it decides which version to install by checking the systems default. If you're defaulted to python3 then you could try aliasing the desired version to "python" and then running the snapcraft command again. I know this solved a similar issue I had when trying to install it for python3 at first because my system was defaulted to 2.7. |
juanrubio
commented
Jul 8, 2016
|
snapcraft supports both python2 and 3. And I believe this is what the log shows
|
popey
commented
Sep 14, 2016
•
|
I also hit this. This appears to be fixed in Snapcraft 2.17, which is in Yakkety and lands in Xenial "soon". So you can probably close this issue I guess. Edit: Spoke too soon. It actually didn't fix it. |
popey
commented
Sep 14, 2016
|
It actually seems like it's just missing creating the build directory as part of the setup. A co-worker provided this output.. http://paste.ubuntu.com/23178423/ root@daydream:/pycryptodome# python2 setup.py -v build_ext |
Legrandin
added
the
bug
label
Oct 16, 2016
Legrandin
closed this
in
#47
Jan 15, 2017
added a commit
that referenced
this issue
Jan 15, 2017
juanrubio
commented
Jan 15, 2017
|
Excellent!. Thanks. |
juanrubio commentedJun 30, 2016
•
Edited 1 time
-
juanrubio
Jun 30, 2016
Hi!,
I'm trying to create a snap package for my project (https://github.com/tizonia/tizonia-openmax-il), and I'm finding this error when pycryptodomex' setup.py is being run.
Pycryptodomex is being pulled as my project depends on 'gmusicapi', and 'gmusicapi' depends on 'pycrodomex'.
It looks like Pycryptodome's setup.py by default assumes a 'build' folder under the distribution root directory, and it looks like there isn't one when all this is being triggered by 'snapcraft'.
I'm not too familiar with either setup.py scripts or snapcraft, so I guess there is a possibility that this could be a snapcraft defect.
(NOTE: tizonia's snapcraft.yaml location is https://github.com/tizonia/tizonia-openmax-il/blob/master/tools/snapcraft.yaml)