Tag Info

Hot answers tagged

5

1) Do I just type cp .bash_profile .bash_profile.ORIG into the terminal right after I open it? Yes. You are essentially making a backup copy of your current ~/.bash_profile (assuming there is one). 2) How do I load it into my text editor? It depends on what text editor you intend to use. I do this: $ emacs ~/.bash_profile but you could also ...


5

When you press Ctrl+C, the process (technically, the process group) that is running in your terminal is killed. You can't resurrect it. All you can do is run it again. Running make involves a lot of steps that each compile a single file, or link some files, or run one test, etc. When you press Ctrl+C, the current step is cancelled, but the data from all the ...


1

As with all questions like this, the answer is to write a PKGBUILD for the package yourself (after you are done, consider putting it on the AUR to make other folks' lives easier :D). Note, you should not ever manually install programs on Arch (or really any distribution with a package manager unless you are willing to deal with manually updating that ...


1

Minor versions like 6.2, 6.3 etc. are designed to be compatible after update (i.e. as long as 6.2 stays 6.2, and upgrades are made within it). Most importantly, kernel major and minor versions as well as glibc major and minor versions will stay the same. Any updates to these will not mean you need to re-compile applications. You would need to re-compile ...


1

You need to also link start up fragments like crt1.o and others if you want to call libc functions. The linking process can be very complicated, so you'd better use gcc for that. On amd64 Ubuntu, you can: sudo apt-get install gcc-multilib gcc -m32 -o test test.o You can see files and commands for the link by adding -v option.


1

I've just finished installing gcc-3.4.6 and gcc-2.95.3 on Ubuntu 14.04 using the steps from the following tutorial. It doesn't make much sense for me to post the steps here because you also need to download some patch files from that page. For both compilations I had to add -D_FORTIFY_SOURCE=0 to the CFLAGS in all the Makefile from the gcc build directory ...



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