186

This is binfmt_misc in action: it allows the kernel to be told how to run binaries it doesn't know about. Look at the contents of /proc/sys/fs/binfmt_misc; among the files you see there, one should explain how to run Mono binaries: enabled interpreter /usr/lib/binfmt-support/run-detectors flags: offset 0 magic 4d5a (on a Debian system). This tells the ...


14

Run this command in your target device export VALGRIND_LIB=~/valgrind/lib/valgrind/ where ./valgrind is installed directory path (given in ./configure)


13

TLDR you need to call arm-linux-gnueabi-gcc not arm-linux-gcc. It looks like you've just got the wrong file name. For reference apt-file is a useful tool. sudo apt-get install apt-file sudo apt-file update apt-file search -x 'gcc$' | grep 'gcc-arm-linux-gnueabi' This searches any file ending gcc in any package with gcc-arm-linux-gnueabi in the name. ...


11

Understanding the Basics From the wiki entry of MIPS architecture, it is described as, MIPS (originally an acronym for Microprocessor without Interlocked Pipeline Stages) is a reduced instruction set computer (RISC) instruction set (ISA) developed by MIPS Technologies (formerly MIPS Computer Systems, Inc.). From the wiki entry of the x86-64, it is ...


11

Now that I'm at work, I'll write up a step by step answer. First off you seem to be doing the steps in the wrong order. As such, I'll number these steps in the order they should be executed. mkdir -pv ~/chromium cd ~/chromium git config --global user.name “Joel Maranhao” git config --global user.email “youremail@example.com” git config --global core....


11

The PS1 shell variable should be set in ~/.bashrc for the bash shell as that is the initialisation file that is read for interactive shell sessions. Note that this variable is a shell variable, not an environment variable (it does not make sense to let child processes inherit its value, and it's only the current shell that uses it). It therefore does not ...


9

As steeldriver suggests, you already have installed the cross-compiler; the problem is that you’re using the wrong command to invoke it, you need to use the arm-linux-gnueabi- prefix in general. So run arm-linux-gnueabi-gcc or arm-linux-gnueabi-g++ and it should work fine. To figure this out yourself, you can use dpkg -L to list the contents of the ...


8

No, you don't have to change any script. It seems like your Buildroot configuration is incorrect, but since you didn't provide your config, there's no real way to give a precise answer. Can you run make savedefconfig and post the output of this file here? Basically, what Buildroot is complaining about here is a mismatch between the kernel headers version it ...


7

Sure, of course, since you can develop portable software that runs on both MacOS and Linux. Be sure to test it on Linux at regular intervals to make sure you haven't unintentionally added something unportable. If you want to use Linux-specific features then you will have more of a hard time. Depending on what it is you do, the program may compile on MacOS ...


6

I made it :-) I basically followed Gilles's advice and decided to do it properly: i.e. manage a complete cross-compilation of GLIBC. I started from crosstool-ng, and was initially disappointed - seeing that it didn't support my old kernel. I kept at it, though - manually editing the configuration file saved by crosstool-ng to do changes like these on the ...


6

You can get a lot of information by means of uname and also by checking with file the type of executables: $ gcc -dumpmachine x86_64-linux-gnu $ uname -o -m x86_64 GNU/Linux $ file /usr/bin/file /usr/bin/file: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=...


5

We first have to set up the multi-arch environment (more info): sudo dpkg --add-architecture armhf sudo apt update Download the source package (using less as an example): apt-get source less Navigate to the directory and, finally, build the package: cd less-458 dpkg-buildpackage -us -uc -b --host-arch armhf The special flag in the command above is --...


5

Host: The environment you are running the compiler on. Target: The environment you are compiling something for.


5

Obviously such machine has no resources, and is not intended for development purposes. For such tasks, you cannot compile blindly in the native architecture of your (Intel) Debian, that is clearly an alien architecture/binaries to your small server. You need to build a cross-compiler (cross)toolchain in a remote machine/in your Debian 7, that compiles ...


5

No, you don't have to cross-compile (that would be necessary if you targeted another architecture.) There are two ways that I can think of that you could set up your systems to do this: Use distcc. The Gentoo and Arch wikis do a good job of describing how to install and configure the program, so I won't copy the entire thing here. Briefly, you need to have ...


4

Emdebian repositories are recommended to be used in stable most of the time since there could be utilities not built in the repositories, packages that were pulled back, etc. If you want to ensure that all your libraries have the correct dependencies, I would suggest stable or testing since they are less likely to have some dependency problem or have ...


4

It seems you are confused between the native compiler and the cross compiler, isn't it ? The commands you tried to use the native compiler : gcc -v gcc -print-prog-name=cc1 You should try ${CCPREFIX}gcc -v ${CCPREFIX}gcc -print-prog-name=cc1 Reading your comments I think you installed the gcc cross-compiler as /home/jorge/tools/arm-bcm2708/arm-bcm2708-...


4

There is a GNU standard naming scheme for compilers and other parts of the toolchain: <target triplet>-<tool name> The target triplet is of the form <machine>-<vendor>-<operatingsystem> And the tool name is gcc for the compiler, or another tool name like ld or strip or ar, etc... The default compiler, the one that compiles ...


4

The Z80 architecture was pretty well known and documented, and had quite an active emulator community. In fact, you still can find a lot of cross-assemblers and related toolchains in Linux distributions. Have a look at the Debian/Ubuntu packages binutils-z80, crasm, d52, pasmo, z80asm, and z80dasm. There is also the package sdcc that is a C cross-...


4

Yes, at least for Autotools-based build systems, as used here (and probably some others); these support a DESTDIR variable which can be used to install somewhere other than /. mkdir destdir make DESTDIR="${PWD}/destdir" install This will give you the target binaries (and accompanying files) in destdir; you can then copy that to the target device's /.


4

The cc1plus you linked is the normal C++ compiler's, not the Windows cross-compiler's. You should never need to fix GCC's internal components; the cc1plus error indicates something else is wrong. In your case, you need to install mingw-w64 (apt-get install mingw-w64). This will install a C and C++ cross-compiler for Windows and the appropriate header files ...


4

You can download a functional toolchain from developer.arm.com and install it manually after removing your existing gcc-arm-none-eabi package. Go to that website, click the "Download" button and get: gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2. Save it in your home directory. Make sure you've uninstalled the old Ubuntu packages. sudo apt remove ...


3

If you look into drivers/usb/serial/Makefile, you'll see that CONFIG_USB_SERIAL_QUALCOMM is responsible for this driver. Execute make menuconfig and goto "Device Drivers"->"USB support"->"USB Serial Converter support"->"USB Qualcomm Serial modem"


3

To run your program on the server, you will need to have the program installed there. You don't need administrator privileges to do this but you will need remote shell access to actually run the program. Your 4th requirement to not leave or install software on the server makes your proposition impossible. If you want to do processing on the server, you ...


3

You need the gcc toolchain for both. The toolchain is part of the android source tree. Before you build the entire android source, you use the "lunch" tool, which sets the environment variables such that a prebuilt toolchain can be used. http://source.android.com/source/building-running.html#choose-a-target The page about compiling the android kernel has ...


3

The error message shows that you want to compile code for your platform (x86/64) with the ARM compiler which does not work. The configure script has not guessed the correct target ("TCC_TARGET_X86_64" instead of the ARM target). Probably, you need the --cpu=armv7a (or what you exactly have) option and/or the --cross-prefix=arm-none-linux-gnueabi- option. ...


3

One reason you may be getting the "missing digest" error (as of 2016 in Gentoo, don't know if this was true in 2013) is that you're using the portage tree from git (thus, with thin manifests which don't contain digests for the ebuilds themselves) while the overlay used for crossdev does not allow that. If that's the case, adding thin-manifests = true to $...


3

The errors are likely from a wrong combination of build variables. The CLFS Build Variable page has detailed explanation on the best combinations of variable settings for different architectures. Similar configure script problems has been solved by changing the CLFS_ARCH variable to thumb For another similar BeagleBoard configure script error, the ...


3

The term platform includes all the details regarding the computer on which the program is compiled or/and run. This means stuff like: CPU: instruction set (x86, x86_64, ARM), endianess (big endian, littel endian) compiler: language (e.g. C90, C99, C11), vendor (GCC, LLVM) libraries, for example glibc and BSD libc, malloc and jemalloc operating system When ...


3

I had the exact same problem and was puzzled. The clue was in the error line: configure: error: invalid feature name: libstdc++-v3 make[1]: *** [configure-gmp] Error 1 evidently the configure-gmp target (in make) was passed the feature name from the parent project. The trick is to spell it out as follows in the command line: --disable-libstdc__-v3 Yes, ...


Only top voted, non community-wiki answers of a minimum length are eligible