I have followed the instructions for installing NZBGet from the official page. I'm installing to a Rasberry Pi on Rasbian Jessie 3. It's 32 bit OS.
Following the installation instructions, when I run:
/nzbget -s
I get the error code:
-bash: nzbget: command not found
It does work when I run it with:
strace ./nzbget -s
Running "file nzbget" returns:
nzbget: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, stripped
The file is definitely in the directory. All users have execute permissions.
Link to my nzbget directory.
The first command starts with a slash. Not a ./
/ Means look in the root directory. ./ Means local
Related
I tried to build a gdb for esp32 that works with qemu, but after many attempt, I didn't manage. All my attempts leaded me to the following error message after connecting to the remote target: Remote 'g' packet reply is too long.
Right now I am using the prebuilt version from Ebiroll: https://github.com/Ebiroll/qemu_esp32/blob/master/bin/xtensa-esp32-elf-gdb
but I would like to use a newer gdb version than 7.10, did anyone had success with this?
Here is how I built gdb:
git clone --depth 1 --branch esp-2021r2-gdb https://github.com/espressif/binutils-gdb.git
cd binutils-gdb
mkdir -p build
cd build
../configure --without-guile --host=x86_64-pc-linux-gnu --target=xtensa-esp32-elf --disable-werror
make
make install
(note from this branch the patch to apply from the Zephyr project, as described here https://github.com/Ebiroll/qemu_esp32#qemu-esp32, seems to already be included)
I also tried by applying the following patch (no success):
curl -L https://raw.githubusercontent.com/Ebiroll/gdb/master/gdb/xtensa-config.c.qemu --output binutils-gdb/gdb/xtensa-config.c
or patching qemu to fix the value of num_regs (tried 104 and 172, also no success).
Espressif's qemu wiki mentions setting an environment variable to only list the core registers:
export QEMU_XTENSA_CORE_REGS_ONLY=1
This needs to be set in the environment from where qemu will be executed.
My recommendation is to use both qemu and gdb (from the Esp32 tool chain) as provided by Espressif. I have recently used this combination with success. The latest release uses gdb 9.2.
I'm using MinGW64 via an MSYS2 download and am currently trying to install the Solar Geometry 2 library (http://www.oie.mines-paristech.fr/Valorisation/Outils/Solar-Geometry/) for use. I'm following their install README, which states to navigate to the directory and "configure" (I've been typing "./configure". However, when I do so, I get the following message in my terminal:
$ ./configure
configure: loading site script /mingw64/etc/config.site
/mingw64/etc/config.site: line 13: config.site:13: default build_alias set to x6_64-w64-mingw32: command not found
/mingw64/etc/config.site: line 20: config.site:20: default prefix set to /mingw4: No such file or directory
configure: error: cannot find install-sh or install.sh in . ./.. ./../..
When I initially installed MSYS2 I set up the etc/fstab file as recommended. However, I'm quite new to MSYS so I'm assuming I botched something in my setup. I haven't edited anything in the config.site file mentioned in the errors, so I'm wondering if it's something in there.
Any help is greatly appreciated, thank you
No where in the directions for "Solar Geometry" do I see reference to MSys or MSys2.
I suggest you install the compiler toolchain and base development file. No idea if you editing /etc/fstab will cause problems. I do not normmaly edit it!
Install MinGW Package build packages. You might need more packages installed.
pacman -S --needed base-devel mingw-w64-x86_64-toolchain
I tried installing Emscripten on the latest version Arch Linux but was unsuccessful. I recieved no errors during the installation process, but when I attempted to verify the installation it threw an error: "bash: ./emcc no such file or directory". To the best of my ability I followed the instrcutions at https://kripken.github.io/emscripten-site/docs/getting_started/downloads.html.
Installation Steps:
1) Dependencies (GCC ships complete with Arch, so no need to install)
pacman -S cmake python2 nodejs git
2) Download and unzip emsdk-portable.tar.gz
mkdir emscripten && cd empscripten
tar -xvf emsdk-portable.tar.gz
3) Installation
cd emsdk-portable
./emsdk update
./emsdk install latest
./emsdk activate latest
source ./emsdk_env.sh
source ./emsdk outputs:
Adding directories to PATH:
PATH += /home/myuser/emscripten/emsdk-portable
Setting environment variables:
EMSDK = /home/myuser/emscripten/emsdk-portable
EM_CONFIG = /home/myuser/.emscripten
Running echo $PATH outputs:
/home/myuser/emscripten/emsdk-portable:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
Running ./emcc -v or ./em++ -v outputs:
bash: ./emcc: No such file or directory
Any thoughts?
Here is my ~/.emscripten file:
import os
SPIDERMONKEY_ENGINE = ''
NODE_JS = 'node'
V8_ENGINE = ''
TEMP_DIR = '/tmp'
COMPILER_ENGINE = NODE_JS
JS_ENGINES = [NODE_JS]
Most usually, a current directory (.) is not added to the PATH variable, AFAIK it is for security reasons, so don't add it yourself too. :) When someone executes ./emcc, they specify the relative path to the program to be executed: "a program emcc residing precisely in the current directory".
On the other hand, executing just emcc (without the ./ prefix) means "iterate through the directories from the PATH variable left-to-right and execute the first found emcc executable". When you source the emsdk_env.sh you, among other things, adjust the PATH variable.
In comments you told that which emcc cannot find the emcc executable. It is strange, but even when you manage to fix the installation problem, you have to most usually specify emcc on the command line without the ./ prefix.
I have an issue with Codelite compilation, running on raspbian jessie - these are the (known) steps I have taken to produce it.
First I installed Codelite with apt-get install Codelite, then produced a c++ project.
When running build project I get the error:
/bin/sh -c ' -j 4 -e -f Makefile'
/bin/sh: 1: -j: not found
0 errors, 0 warnings
I note that this error has been found and corrected previously, through running a different version of Codelite from 6.1.1 (that which apt-get installs). I therefore found the updated version of armhf .deb codelite from the rasbian archive with gdebi-gtk. However the updated version (9.1.1) produces the following error (install attempt with the graphical debian):
Error: Dependency is not satisfiable: libclang 1-3.8 (>=3.2)
I do not understand why the package manager cannot update these packages - do they not exist for the pi? I ran the manager as root, so I do not think it is a permissions issue.
EDIT 1:
Thank you for that Fabre. My Enviromental Variables file now looks like this:
CodeLiteDir=/usr/share/codelite
export MAKE=make
I still get the same error however.
I want to compile gcc-2.95.3 on my Ubuntu 12.04 machine, but it won't work.
I found this, and this, but nothing helped.
I first tried to build it with my 4.6.3 version of gcc, but I got an error message.
Then I tried to build gcc-3.4.6 because in the first link, this version had been used to build 2.95.3, but it was not successful either.
Trevorpounds is the best page solving this issue you can find, but it just wont work.
I tried other things too, but nothing works.
As far as I know, the newer toolchain may be the problem, but is there some way to fix that without reinstalling the whole OS?
Actually, I dont even care whether I build it myself or not, if there is a place where I can download the binaries and they work, i'm happy.
Okay, the detailed information what I did and what error messages I got:
The whole procedure is from here
1) I have a fresh installation of Ubuntu 12.04
2) I detect what glibc I have installed by ldd --version, I got the answer ldd (Ubuntu EGLIBC 2.15-0ubuntu10.5) 2.15 ... so it is 2.15
3) I download glibc-2.15.tar.gz from http://ftp.gnu.org/gnu/libc/, I save it into my Downloads folder.
4) I unpack glibc by tar xzf glibc-2.15.tar.gz
5) mkdir -p gcc-2.95.3/glibc-workaround/include/bits
6) cp glibc-2.15/bits/stdio-lock.h gcc-2.95.3/glibc-workaround/include/bits
7) cp glibc-2.15/nptl/sysdeps/unix/sysv/linux/x86_64/bits/pthreadtypes.h gcc-2.95.3/glibc-workaround/include/bits
8) sed -i -n '1h;1!H;${;g;s/\(__pthread_slist_t __list;\n[ \t]*}\)/\1 __gcc_295_workaround__/g;p;}' gcc-2.95.3/glibc-workaround/include/bits/pthreadtypes.h
9) Now I download gcc-2.95.3.tar.gz from ftp://ftp.gnu.org/gnu/gcc/, I also save it in my Downloads folder.
10) I unpack gcc by tar xzf gcc-2.95.3.tar.gz
11) cd gcc-2.95.3
12) I download http://www.trevorpounds.com/blog/wp-content/uploads/2010/01/gcc-v2.95.x.debian.x86_64.diff and save it into the Downloads folder.
13) patch -p0 < ../gcc-v2.95.x.debian.x86_64.diff no errors occur
14) mkdir ../gcc-2.95.3-objdir
15) cd ../gcc-2.95.3-objdir
16) ../gcc-2.95.3/configure --prefix=/opt/i386/gcc/gcc-2.95.3 --enable-languages=c,c++ --enable-threads=posix --enable-shared --host i386-pc-linux-gnu seems to work fine
17) make > log.txt
This is where I get my error
I get this in the console:
and this is my log.txt file:
18) The next step would be make install but I didn't do that, since I got the error before.