Tag Archives: linux basics

[Solved] CentOS Install pycrypto Error: RuntimeError: autoconf error

Solution:  yum -y install gcc

 

File "/usr/lib64/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/usr/lib64/python3.6/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib64/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib64/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/tmp/pip-build-ydg0qryh/pycrypto/setup.py", line 251, in run
self.run_command(cmd_name)
File "/usr/lib64/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib64/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/tmp/pip-build-ydg0qryh/pycrypto/setup.py", line 278, in run
raise RuntimeError("autoconf error")
RuntimeError: autoconf error

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

Error response from daemon: OCI runtime exec failed: exec failed: container_linux.go:345:

        An error was reported when using docker to enter the specified container today. The screenshot of the error is as follows:

        After careful verification, the command is correct, but it can’t get into the container. After checking the data, it is realized that there is a problem with the docker. It can be understood in combination with the error report:

Error response from daemon: OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown

        The above is complete error reporting information, of which the key information is as follows:

"/bin/bash\": stat /bin/bash: no such file or directory": unknown

        That is, there is no directory/bin/bash, so an error will be reported when you want to enter the container according to the initial command.

        You can enter by using the following command. The screenshot is as follows:

docker exec -it mqtt /bin/sh

      Perfect solution, record notes!

 

Virtualbox failed to attach usb, VERR_PDM_NO_USB_PORTS problem solved

The problem described
Error:VERR_PDM_NO_USB_PORTS
my machine environment:
host kali Linux virtualbox version 5.0.x
Question why
Usb Settings should use USB 3.0, as if because VirtualBox doesn’t support anything else
Problem solving
Settings Go to USB Settings and select USB 3.0 but Invalid Settings Detected appears. Tip need to install the Extension pack. And go to the website to download the Extension pack, then warrant 5.1.1 version seems finally to version, so the final solution is to update the virtualbox.
but here are a few need to be aware of, update need completely remove clean before virtualbox virtualbox

apt-get remove virtualbox
apt-get remove virtualbox-dkms

After that, I used the official downloaded.deb file for the installation

dpkg -i virtualbox-5.1_5.1.6-110634~Debian~jessie_amd64.deb

Prompt lack of libvpx1 and libssl1.0.0
apt-get found that these two can not directly down,libvpx is related to libvpx3 and libvpx4, it seems that must be libvpx1 can, so there is no way, can only search libvpx1 and libssl1.0.0, here is my search to download the address
libssl1.0.0 download address
libssl1.0.0 download address
libvpx1 download address
and then respectively through DPKG After the -i installation, install Virtualbox-5.1 and open Discover USB is now available. The default is 3.0