I am on Ubuntu 8.04 and I have just downloaded Boomerang and unzip the files into a folder on my desktop.
I cd into that folder where the exe boomerang file resides, and typed ./boomerang and boomerang.
However I got the error message:
unable to execute ./boomerang: No such file or directory.
Why does this happen?
I guess, you're on a 64 bit system, which mean you must install some x86 libraries to run the program,
to list the libraries the binary is linked against, run readelf -d | grep NEEDED
once you know the libraries, just install it for x86 architecture: here are some common and necessary libraries for x86
sudo apt-get install libgc1c2:i386 libexpat1-dev:i386 lib32stdc++6 lib32z1 lib32z1-dev
now the program should start normally,
but if it persists, you should see a different kind of error,
try to install those libraries for x86
make sure you have Qt installed for the GUI version.
The error is most likely because you have a 64-bit system, but the boomerang binaries are 32-bit, and many newer 64-bit systems no longer ship with 32-bit support.
The solution is to install 32-bit support for your system; the method for doing this may differ, however the procedure I used was:
sudo apt-get install -y lib32z1 lib32ncurses5 lib32bz2-1.0
Which should be compatible with Ubuntu and many derivatives, though you should look up the correct procedure for your particular OS version, rather than simply running this command.
However, there may also be a number of other 32-bit libraries that are still required before boomerang will run on a 64-bit linux distribution, but at least once you have 32-bit support installed it can tell you what these are!
Are you sure you unpacked it ??
weewee#ubuntu:~/Downloads$ tar xzf boomerang-linux-alpha-0.3.tar.gz
weewee#ubuntu:~/Downloads$ cd boomerang-linux-alpha-0.3/
weewee#ubuntu:~/Downloads/boomerang-linux-alpha-0.3$ ls -l boomerang
-rwxr-xr-x 1 weewee weewee 2376620 Jun 13 2006 boomerang
weewee#ubuntu:~/Downloads/boomerang-linux-alpha-0.3$ ./boomerang
Boomerang alpha 0.3 13/June/2006
Usage: boomerang [ switches ] <program>
boomerang -h for switch help
Related
abigail#abilina:~/Downloads$ sudo dpkg -i cuda-repo-ubuntu1604_8.0.61-1_amd64.deb
Selecting previously unselected package cuda-repo-ubuntu1604.
(Reading database ... 205999 files and directories currently installed.)
Preparing to unpack cuda-repo-ubuntu1604_8.0.61-1_amd64.deb ...
Unpacking cuda-repo-ubuntu1604 (8.0.61-1) ...
Setting up cuda-repo-ubuntu1604 (8.0.61-1) ...
Warning: The postinst maintainerscript of the package cuda-repo-ubuntu1604
Warning: seems to use apt-key (provided by apt) without depending on gnupg or gnupg2.
Warning: This will BREAK in the future and should be fixed by the package maintainer(s).
Note: Check first if apt-key functionality is needed at all - it probably isn't!
Warning: apt-key should not be used in scripts (called from postinst maintainerscript of the package cuda-repo-ubuntu1604)
OK
abigail#abilina:~/Downloads$ sudo apt-get install cuda
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
cuda : Depends: cuda-8-0 (>= 8.0.61) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
My ubuntu version is 17.04. Does this mean my Linux currently can't install CUDA? I want to install TensorFlow with GPU support.
Per suggestion:
abigail#abilina:~/Downloads$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
https://launchpad.net/ubuntu/zesty/amd64/nvidia-cuda-toolkit
above is the correct one.
apt-get install nvidia-cuda-toolkit
but remember the cuda installed through apt were installed in different location. manually create ln -s at /usr/local/cuda for include,lib64,and bin
I have successfully installed CUDA 8.0 + the latest patch from NVIDIA on Ubuntu 17.04:
Download the .run file from https://developer.nvidia.com/cuda-downloads, choosing Ubuntu 16.04 (Base Installer)
You will not be able to install it by just running, because it is looking for a file called InstallUtils.pm which is not present in Ubuntu 17.04, but curiously, is present in the .run file - so: unpack the .run file using ./cuda*.run --tar mxvf
copy InstallUtils.pm (should be in the /bin path) to /usr/lib/x86_64-linux-gnu/perl-base
Run the installer (You may want to say no to the driver install step to keep the one you install through apt - I'm using 381.22, because 375.26, which is provided by the .run file does not support my 1080ti)
gcc 6 is incompatible with CUDA, but this is easily remedied for compiling the sample files: just add export EXTRA_NVCCFLAGS="-Xcompiler -std=c++98" to your bashrc file, and comment out
from one of the headers (I think it was host_config.h, but you'll see it once you try to compile) - comment out these lines:
#if __GNUC__ > 5 || (__GNUC__ == 5 && __GNUC_MINOR__ > 3)
#error -- unsupported GNU version! gcc versions later than 5.3 are not supported!
This is all from memory, so hopefully it's accurate enough.
I managed to find this solution thanks to these useful posts:
https://devtalk.nvidia.com/default/topic/983777/can-t-locate-installutils-pm-in-inc/
https://devtalk.nvidia.com/default/topic/949770/cuda-8-0rc-supporting-gcc6-/
For ubuntu 17.04, I had to use cuda 9.0 (deb version)
https://developer.nvidia.com/cuda-release-candidate-download
I couldn't get it to work otherwise. Cuda 8.0 needs gcc 5.3.1 but cuda 9.0 is compatible with gcc 6.3.0 which is installed on ubuntu 17.04 automatically.
More precisely, this is what I did:
On Ubuntu 17.04, install CUDA 9.0 — you can currently download the beta version
https://developer.nvidia.com/cuda-release-candidate-download
I downloaded the .deb file and haven’t had any problems — follow the steps they recommend when you download cuda 9.0
sudo dpkg -i cuda-repo-ubuntu1704-9-0-local-rc_9.0.103-1_amd64.deb
sudo apt-key add /var/cuda-repo-9.0-local-rc/7fa2af80.pub
sudo apt-get update
sudo apt-get install cuda
Then follow the post installation steps from the nvidia instructions (i.e., setting PATH and LD_LIBRARY_PATH)
http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#post-installation-actions)
export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64 ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
Cuda 9 is compatible with gcc 6.3.0 (which comes with 17.04). I used arch=sm_52 and sometimes for my make files have to go ‘make clean’.
Installing Cuda 9.0 was the simplest solution in my case.
Alternatively, if you'd prefer cuda 8, you can download the deb file and then use the command
dpkg-deb -x cuda_8.*.deb /usr/local/cuda-8.0
to extract the contents from the deb file and have them placed in the desired directory.
Source: http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#advanced-setup)
I downloaded the current version of Android Studio (latest as of 4th July 2013)
I also downloaded the JDK version 7u25.
However, it displays error after startup: Please ensure JAVA_HOME points to JDK rather than JRE.
I don't know how to solve this problem, which won't let me run the IDE. I would appreciate any help.
Check if java JDK is installed correctly
dpkg --list | grep -i jdk
if not install JDK
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update && sudo apt-get install oracle-jdk7-installer
After the installation you have enable the jdk
update-alternatives --display java
Check if Ubuntu uses Java JDK 7
java -version
If all went right the answer should be something like this:
java version “1.7.0_25″
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.3-b01, mixed mode)
Check what compiler is used
javac -version
It should show something like this
javac 1.7.0_25
Add JAVA_HOME to environment variable
Edit /etc/environment and add JAVA_HOME=/usr/lib/jvm/java-7-oracle to the end of the file
sudo nano /etc/environment
Append to the end of the file
JAVA_HOME=/usr/lib/jvm/java-7-oracle
Log in and out (or reboot) for the changes to take effect.
If you want to remove oracle JDK
sudo apt-get remove oracle-jdk7-installer
read this:
http://arwankhoiruddin.blogspot.co.il/2014/01/android-studio-in-ubuntu-problem.html
in short:
type at the terminal
$ sudo update-alternatives --config java
now you need to choose
usr/lib/jvm/java-7-openjdk/jre/bin/java
by pressing #3
I have Ubuntu 14.04 and OpenJDK and for me a fresh install worked.
just did
sudo apt-get install openjdk-7-jdk
or,
sudo apt-get install --reinstall openjdk-7-jdk if it is already installed and giving error,
and everything was fine.
On ubuntu I have tried all the methods that are described here but none worked.
What I did in the end was to:
download JDK from oracle and extract the archive
edit android-studio/bin/studio.sh and add at the top
export JAVA_HOME=/path/to/jdk
save the file and cd android-studio/bin and launch Android Studio: ./studio.sh
On Fedora (and other RedHat derivatives, e.g. RHEL 7 and CentOS 7), it was the missing openjdk-devel package that was the issue for me. It's an easy fix and nothing to do with the JAVA_HOME path or the JRE.
sudo yum install java-1.7.0-openjdk-devel.x86_64
If you are using Windows, the installation can be confusing for many users...
The installer lets you specify an installation path, but this is only if you have the JRE option selected to install.
The actual JDK installs automatically to...
C:\Program Files\Java\jdkX.XX on 64-bit
C:\Program Files (x86)\Java\jdkX.XX on 32-bit
So you need to make sure you set the JAVA_HOME variable in environment variables set to this JDK path, not the JRE path that appears in the installer.
In windows Create new environment as STUDIO_JDK which refers to your jdk C:\Program Files\Java\jdk1.7.0
This answer may be very specific to a Windows 7 32 bit system:
Even after setting the JAVA_HOME variables, I had problems. After installing the JAVA again from the website, http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
BUT THIS TIME I TRIED "Windows x64 54 MB jdk-8u51-windows-x64-demos.zip" which seems to be for 64 bit even though my system is 32 bit and the ANDROID STUDIO started working for me. My environment settings are following (under System variables and not under user variables):
JAVA_HOME-C:\Program Files (x86)\Java\jre1.8.0_51
JDK_HOME-C:\Program Files (x86)\Java\jdk1.8.0_51
I had the same problem on Linux Mint 17.2 and it was very simple:
In the package manager I found that openjdk-7-jre was installed but not the JDK. All I had to do was to install openjdk-7-jdk.
As I'm new to Linux it took me some time to figure this out though because I assumed by the name of the path /usr/lib/jvm/java-7-openjdk-amd64 that it was already the JDK but it was just the JRE.
On Linux Mint 17 (or Ubuntu 14.04):
sudo apt-get install openjdk-7-jdk
Then change the JAVA_HOME env variable.
export JAVA_HOME=JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/
Downloading the latest Android Studio resolve this issue / OSX /MAC
is it possible to run Google's Big Query command line tool: gsutil on Windows 7 64 bit?
I could not get this to work because of a dependent Python module called: pyOpenSSL-0.13, which I could not install w/o building it using Microsoft Express 2008. Just wondered if this was a known issue.
Thanks.
OK. I finally came up with a solution for those with a similar problem:
Install cygwin w/ dev tools (i.e. gcc compiler, make, automake, etc)
Install openssl-dev for cygwin.
Download pyOpenSSL-0.13 gzip file and decompress it into home folder. (Google for this)
run "python setup.py install" from inside a cygwin prompt.
Download gsutil source code from Google and decompress it into home folder.
run "python setup.py install" from inside a cygwin prompt.
cd to the gsutil directory
run ./gsutil
This solution worked for me on a 64 bit Windows 7 machine. It could be that I broke my installation and that others may not run into this problem. However, it does seem that OpenSSL support for gsutil on a Windows 64 bit machine running 64 bit python is non-existent.
I am a novice with zeroMQ and I am stuck at binding ØMQ with java on a server running CentOS release 5.9.
Unfortunately, I do not have super user/root privileges on the server and am trying to install ØMQ as a normal user with restricted privileges. I have installed ØMQ by following instructions on http://www.zeromq.org/area:download
Make sure that libtool, autoconf, automake are installed.
Check whether uuid-dev package, uuid/e2fsprogs RPM or equivalent on your system is installed.
Unpack the .tar.gz source archive.
Run ./configure, followed by make.
Could not run the following obviously
To install ØMQ system-wide run sudo make install.
On Linux, run sudo ldconfig after installing ØMQ.
Then I attempted to install jzmq.
Cloned [git clone https://github.com/zeromq/jzmq.git]
Ran autogen.sh
Ran configure
At this point I get the following error
checking for ZeroMQ... no
checking zmq.h usability... no
checking zmq.h presence... no
checking for zmq.h... no
configure: error: cannot find zmq.h
As a result of the above error I am not able to run java tests and get error "no jzmq in java.library.path".
Can anybody help/direct me to how to get java binding for zeromq work when you dont have root privileges to install it? Its difficult to get IT department to install a new software on servers.
Appreciate your help.
Note: I do not have write permissions to /usr directory
Thanks
GBP
This can be overcome by adding --with-zeromq=/home/user/zeromq (installation directory of zeromq)
./configure --with-zeromq=/home/user/zeromq
Other steps include
export LD_LIBRARY_PATH=/home/user/zeromq/lib
You can also use JeroMQ (https://github.com/zeromq/jeromq) which is a pure Java implementation of ZeroMQ
I got this working by running autogen.sh on OEL 6 then running configure / compiling / installing on CentOS 5.9. I briefly looked into why autogen.sh was failing and the problem was the tool chain was too old. Since I had a more up-to-date system with a modern tool chain available running autogen.sh on something other than CentOS 5 was the easiest path for me. I'm sure it works fine with other modern Linux variants, I had OEL 6 at my finger tips.
I also did not have access to a standard directory for installation. To get that working I added zmq.jar to my class path, and the run-time linker needed to be able to find the zeromq and jzmq run-time libraries.
I faced the same issue on CentOS 6.5 and found that you need to install "gcc-c++" for this to work.
I used the following to install dependencies:
yum -y install jdk zeromq-devel unzip libtool gcc autoconf automake gcc-c++ python
Note that "jdk" comes from our private repository and it's same what can be downloaded from java.com
The following public repositories are installed on server:
atomic
Actually, I ended up having this same issue, and the following script worked for me, where I installed zeromq into ~ (so that I have ~/lib contains libzmq.a libzmq.la libzmq.so libzmq.so.3 libzmq.so.3.1.0 pkgconfig)
./autogen.sh ./configure --prefix=$HOME \ #because you don't have root privileges
--with-zeromq=$HOME --includedir=$HOME/include/ --libdir=$HOME/lib/
./make
./make -n install
#to check to see if it installs it to the right location
make install
Has anyone successfully cross-compiled mono for ARM under Linux without scratchbox or qemu?
(maybe with distcc or some cross-compiler toolchain)
I managed to cross compile mono(2.0, 2.4, 2.6, 2.8, 2.10.1) with Scratchbox 2 installed on a Ubuntu machine using CodeSourcery Lite tool chain. I used the article from the Mono project page.
First compile it on the native machine
./configure
$ make
$ make install DESTDIR=path
Then in sb2:
[sbox-ARMEL: ~] > ./configure --disable-mcs-build
[sbox-ARMEL: ~] > make
[sbox-ARMEL: ~] > make install DESTDIR=path
I use this for configuration
./configure --enable-minimal=profiler,debug,logging,soft_debug --with-tls=--with-tls=__thread --with-monotouch=no --without-mcs-docs --disable-mono-debugger CFLAGS=-DARM_FPU_NONE --disable-mcs-build
I tried and tried and tried with scratchbox2 last night.. Ran into some problem.. Ended up just compiling on arm, went fine! took 30 minutes!
CFLAGS=-DARM_FPU_VFP_HARD HardFloat
CFLAGS=-DARM_FPU_VFP_NONE SoftFloat
Compile mono on PC
sudo make install `directory like /tmptree etc`
move all these files from /tmptree over to / etc on your arm device.
./autogen.sh --disable-mcs-build
make CFLAGS=-DARM_FPU_VFP_HARD
sudo make install
sudo ldconfig
Mono Hard Float Patch
Tried doing Hard Float with mono 3.0.3.. it said it didn't support it yet.