I have a 32 bit Ubuntu on Linode, confirmed by:
~$ uname -m
i686
Following the install instructions I get:
~$ wget https://s3.amazonaws.com/influxdb/influxdb_latest_i686.deb
...
Length: 16572810 (16M) [binary/octet-stream]
Saving to: `influxdb_latest_i686.deb'
100%[======================================>] 16,572,810 2.43M/s in 7.3s
2015-03-31 15:59:28 (2.16 MB/s) - `influxdb_latest_i686.deb' saved
~$ sudo dpkg -i influxdb_latest_i686.deb
dpkg: error processing influxdb_latest_i686.deb (--install):
package architecture (i686) does not match system (i386)
Errors were encountered while processing:
influxdb_latest_i686.deb
I tried the amd64 package as well, and got the same error.
Any ideas?
InfluxDB no longer provides i386 binaries, you would need to compile from sources.
I managed to install 0.8 with dpkg -i --force-architecture influxdb_0.8.8_i686.deb but 0.9 won't work
From https://influxdata.com/downloads/
About 32-Bit Packages
The industry is gradually moving away from
support for 32-bit x86 architectures so we do not provide packaged
32-bit binaries. However, we do endeavour to ensure the source can be
compiled for a 32-bit x86 architecture at all times. To that end our
CI system currently compiles 32-bit binaries and runs the unit test
suite against the 32-bit build, in addition to the main 64-bit build.
If compilation or unit testing for 32-bit architecture fails, we fix
it.
Related
I’m try to use picamera, raspistill on raspberry pi.
I recognized that these modules are Only work in 32bit os.
But I want to use another development that works in 64bit os.
So my question is this.
Is it possible to make or install container that is different from host os?
Host: 32bit, Container: 64bit
I think docker officially support 64bit os. so this will be not... right?
Host: 64bit, Container: 32bit
If it will be OK. Can I mix my local 64bit function and Container 32bit function?
There is a feature to run multiple architectures on the same kernel. I use this to run i386 binaries in an amd64 container on an amd64 host OS/kernel.
Debian call this Multiarch. I haven't tried this on arm, but in theory this could work the same as on Intel.
Look at the Multiarch HOWTO:
use a base container for an architecture in your Dockerfile, e.g. image=debian:buster-slim
add another architecture: dpkg --add-architecture armhf
update package list: apt-get update
install the tools and libraries for the respective architecture (e.g. armhf or arm64): apt-get install -y yourpackage:armhf
As I said I only used that for i386, there might be more pitfalls with arm.
/edit: I use the same now also for a ARM64 Linux running armhf binaries (32 bit) in a docker container.
~$ nvidia-smi
nvidia-smi: command not found
~$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Tue_Jun_12_23:07:04_CDT_2018
Cuda compilation tools, release 9.2, V9.2.148
Its worked before. I made changes in grub using the command
gksu gedit /etc/default/grub
but revert it back. (I don't know if it could have effect)
Reason
The most common reason for any “command not found” error is that the software being accessed is not installed on the system. Check out the example below where the tool is not installed on the system and the error “nvidia-smi command not found” is thrown:
Solution
The best way of resolving this error is to install the “nvidia-utils” package which will also contain the “nvidia-smi” tool inside it. To install this package, run the command in the terminal:
$ sudo apt install nvidia-utils-515
I got the detailed solution form this post: https://itslinuxfoss.com/fix-nvidia-smi-command-not-found-error/
I'm trying to compile OpenCV to use it on a ODROID-UX3 machine (ARM architecture) with Ubuntu 14.04. Following the guide on the OpenCV website I'm trying to install the cross compilation tools (gnueabihf) with no luck. Apt-get doesn't seem to locate the package gcc-arm-linux-gnueabihf. Is there a compatibility issue?
No, Ubuntu has a package named gcc-arm-linux-gnueabihf
here:
Package: gcc-arm-linux-gnueabihf (4:4.6.2-7) [universe]
The GNU C compiler for armhf architecture
Your problem is something else.
I would like to install LuaJIT on my redhat system...in order to get OSRM working. I have tried to do so by following the instructions here
and in particular i was following this part:
cd /tmp
wget http://luajit.org/download/LuaJIT-2.0.2.tar.gz
tar -zxvf LuaJIT-2.0.2.tar.gz
cd LuaJIT-2.0.2
make install PREFIX=/opt/osrm_infrastructure/LuaJIT-2.0.2
however i get the following error:
==== Building LuaJIT 2.0.2 ====
make -C src
lj_arch.h:324:2: error: #error "No support for PowerPC 64 bit mode"
#error "No support for PowerPC 64 bit mode"
^
I am on a redhat 7 ppc64 architecture...
Is there a work around that might be available?
Try using LuaJIT 2.1 from this fork, which has support for PowerPC 64-bit Little Endian (ppc64le). It it was not tested with OSRM, but it works with some Lua software.
Situation:
In my Mac Os 10.8.5 I have available python2.7 and python2.7-32 with latest cx_freeze(-4.3.2).
I need cx_freeze to pick the python2.7-32 version so my executable app can use a 32-bit version of OpenCV.
So far, all attempts to use cx_freeze script suggest that it bundles python2.7(which is 64bit) and the app fails to execute with: "cv2.so: mach-o, but wrong architecture"
(This is the same error you would get if you try to import OpenCV built in 32 bits, with a python interpreter of 64)
Is there a way to "force" cxfreeze to bundle a specific python version installed (in this case python2.7-32) in the executable it produces?
Edit:
I've also tried to build cx-freeze from source in 32-bit using:
python2.7-32 setup.py build;
python2.7-32 setup.py install
No matter what, the app generated is still a 64bit version:
$ python2.7-32 setup.py bdist_dmg
$ file capturebasic
capturebasic: Mach-O 64-bit executable x86_64
$ arch -i386 ./capturebasic
arch: posix_spawnp: ./capturebasic: Bad CPU type in executable
Edit2:
It seems that Mac's cx_freeze you download from sourceforge is only 64-bit:
http://sourceforge.net/projects/cx-freeze/files/4.3.2/
If you want to create 32-bit apps, you need the 32-bit version of cx_freeze.
I'm confirming if there's any way to install the 32bit version in Mac in cx_freeze's mailing list.
I believe you do not have to touch your setup script, but just change the command used to build it. For instance instead of using python setup.py build, you would use the command python2.7-32 setup.py build. You may have to specify the path to the python2.7-32 exe. so something like path\to\python2.7-32.exe setup.py build. Note: I use windows so the example commands I used might be a little different on mac, like instead of .exe it's .app.
Hope this helped.