Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [xacc-dev] XACC Builds?

 Error - cannot import XACC Python Bindings 

​On this point, make sure that xacc-framework, which is a python script, is being executed with the same python that was used in the pip install command. From your output it looks like you might have run 'pip install' and then xccc-framework is being executed with python3, so try 'pip3 install'. 

As for the first error - I've seen this internal compiler error: Killed before when I was running in a docker container/daemon that did not have a enough RAM allocated to it. Either increase your Docker daemon's memory usage or maybe make sure that you run 'make install' instead of 'make -j4 install' or -j$NPROCS. 

From: Justin Crites <jc@xxxxxxxxxxxxxxxx>
Sent: Wednesday, April 11, 2018 5:04 PM
To: McCaskey, Alex
Subject: Re: XACC Builds?
Yeah, trying pip install failed as so: 

++: internal compiler error: Killed (program cc1plus)
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
    CMakeFiles/xacc.dir/build.make:62: recipe for target 'CMakeFiles/xacc.dir/XACC.cpp.o' failed
    make[5]: *** [CMakeFiles/xacc.dir/XACC.cpp.o] Error 4
    make[5]: *** Waiting for unfinished jobs....
    CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/xacc.dir/all' failed
    make[4]: *** [CMakeFiles/xacc.dir/all] Error 2
    Makefile:138: recipe for target 'all' failed
    make[3]: *** [all] Error 2
    CMakeFiles/xacc-core.dir/build.make:115: recipe for target 'xacc-core-prefix/src/xacc-core-stamp/xacc-core-build' failed
    make[2]: *** [xacc-core-prefix/src/xacc-core-stamp/xacc-core-build] Error 2
    CMakeFiles/Makefile2:180: recipe for target 'CMakeFiles/xacc-core.dir/all' failed
    make[1]: *** [CMakeFiles/xacc-core.dir/all] Error 2
    Makefile:127: recipe for target 'all' failed
    make: *** [all] Error 2
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-d5i52h73-build/", line 115, in <module>
      File "/usr/lib/python3.5/distutils/", line 148, in setup
      File "/usr/lib/python3.5/distutils/", line 955, in run_commands
      File "/usr/lib/python3.5/distutils/", line 974, in run_command
      File "/usr/lib/python3/dist-packages/setuptools/command/", line 61, in run
      File "/usr/lib/python3.5/distutils/command/", line 583, in run
      File "/usr/lib/python3.5/distutils/", line 313, in run_command
      File "/usr/lib/python3.5/distutils/", line 974, in run_command
      File "/usr/lib/python3.5/distutils/command/", line 135, in run
      File "/usr/lib/python3.5/distutils/", line 313, in run_command
      File "/usr/lib/python3.5/distutils/", line 974, in run_command
      File "/tmp/pip-d5i52h73-build/", line 45, in run
      File "/tmp/pip-d5i52h73-build/", line 82, in build_extension
      File "/usr/lib/python3.5/", line 581, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j4']' returned non-zero exit status 2

Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-d5i52h73-build/';f=getattr(tokenize, 'open', open)(__file__);'\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-p9vm0i_d-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-d5i52h73-build/

Installing the original way using cmake works but installing the packages using xacc-framework leads to this error: Error - cannot import XACC Python Bindings 

On Wed, Apr 11, 2018 at 3:33 PM McCaskey, Alex <mccaskeyaj@xxxxxxxx> wrote:
Hey Justin,

I have been working on a pip installer for xacc. But you can still build the same way as before. The one difference is that is now xacc-framework since I plan to turn this into a utility executable that is for the framework in general and not just for installing plugins.

If you go the old route, by default CMAKE_INSTALL_PREFIX is now $HOME/.xacc (unless you change it when you configure). This will give you $HOME/.xacc/bin/xacc-framework that you can use as usual (-p tnqvm ibm etc.) to install plugins. The plugins will be installed to $HOME/.xacc/plugins.

If you pip install, you can just run pip install . (I use --user argument), and xacc will be installed to your Python site-packages folder, and there will be a corresponding bin directory in this Python installation (on fedora it’s $HOME/.local/bin and and Mac its ~/Library/Python/VERSION/bin) with xacc-framework.

Also, I’m working off the Eclipse project now, and the ORNL-QCI will soon be a mirror repository for the Eclipse one. Just so you know.

If you send me your error message I can probably help you figure out exactly what caused the build failure.


> On Apr 11, 2018, at 3:53 PM, Justin Crites <jc@xxxxxxxxxxxxxxxx> wrote:
>  Hey Alex,
> My Docker builds have started breaking as I was finishing up the Kubernetes integration. I noticed you started switching the builds over to a to I'm guessing use a pip install method to build the repo.
> Is the new setup path "pip install ." then install the plugins via the same "" path?

Back to the top