Hot answers tagged toolchain
The Cross compiler article on wikipedia is quite good. Generally a cross compiler is a compiler producing code for a different kind of system than yours. Usually this means a different target hardware architecture, but it can also mean a different target operating system (or both). Theoretically you could combine these and use a cross-compiler on ...
On Debian, there are apt-cross and dpkg-cross from Emdebian, which let you set up cross-compilation for many architectures (you get cross-compilers and libraries). On Ubuntu, there's a crosschain for ARM, and a project to improve on this. You can also create toolchain using crosstool-ng which is not link to a distribution.
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 ...
When you want the program a.out to read the output of the command echo 0 as its input, then you can do that like this: echo 0 | ./a.out Or (this is bash specific): ./a.out < <(echo 0) This > and this < instead are redirection operators, > is the redirection of the output and < of the input. This: echo 0 > input.txt Redirects ...
As far as I know it is not possible. Please remember that toolchain does not exist in vaccum and is interlinked. What might work is to build cross-compiler of new infrastructure but I really doubt it - the "atomicity" on update of glibc will break everything. I would advice backup & reinstall of system.
Have you tried downloading the amd64 stage3 tarball and using the copy of gcc with that?
If your kernel is 64-bit (and so you can run 64-bit binaries), you can start a new x86_64 Gentoo install in a chroot, following the usual instructions. I've done similar before — effectively a reinstall, but while still running the old system. If you don't have a spare block device to install to, you can use a subdirectory and either boot with ...
Problem GLIBC 2.12 is installed and as the OP's title states, the cross compile toolchain he is trying to use requires GLIBC >2.14. The OP states that he is also constrained because he cannot update the system. Caveats The list below in step 3 is used to build the changeroot. When possible use the packages included from your distributions repositories. ...
Probably not as elegant as you may wish, but I'd use wmctrl for this. xterm -T mail.log -e tail -f /var/log/mail.log & until wmctrl -F -r mail.log -e0,<posx>,<posy>,<width>,<height> do sleep .1s done Of course you may use other apps than xterm. wmctrl can only match window titles or window IDs. If you cannot set your window ...
I've found the problem(s): as Munir staded, I had sh pointing to dash instead of bash; after that, gcc failed to compile because of the missing rpc/xdr.h header; this was fixed by rebuilding the glibc by adding the flag: --enable-obsolete-rpc; All is fine now.
You can try to install apt-get install lib32stdc++6
What you could do is download Ubuntu .iso on your computer, then use SFTP (FTP via SSH) to upload .iso file to your server. On your server you can mount the .iso file like this: mkdir /mnt/ubuntu_iso mount -o loop /path/to/file.iso /mnt/ubuntu_iso Now edit /etc/apt/sources.list file and comment out everything that is not cd-rom related. Then run ...
Only top voted, non community-wiki answers of a minimum length are eligible