HOw To Install & Configure Ubuntu 24.04.2

1. GET THE ISO
2. BURN THE ISO TO DISC(LOAD DISKS)
3. BOOT THE ISO
4. CHOOSE UPDATE INSTALLER
5. BOOT THE UPDATED INSTALLER
6. CHOOSE USE WIRED CONNECTION (BETTER TO BE USING THIS OPTION TO CONNECT TO THE INTERNET, CURRENTLY)
7. CHOOSE INSTALL UBUNTU INSTEAD OF TRY UBUNTU
8. CHOOSE EXTENDED SELECTION
9. CHOOSE INSTALL THIRD PARTY SOFTWARE FOR GRAPHICS AND DOWNLOAD AND INSTALL SUPPORT FOR ADDITIONAL MEDIA FORMATS
10. ERASE DISK AND INSTALL UBUNTU OR MANUAL INSTALLATION
11. IF YOU CHOSE MANUAL INSTALLATION, MAKE A SWAP PARTITION THAT IS 16 GIGABYTES, AN EFI PARTITION THAT IS 1 GIGABYTE, AND THE REST YOUR ROOT PARTITION, **** MUST FILL THE REST OF THIS OUT AFTER BOOTING THE ISO

REMEMBER TO DO THAT ^ **** BEFORE POSTING

ONTO INSTALLING PYPY 2.7 AND PYPY 3.11 BUILT USING A 16TH GEN GCC, VERY FAST!

1. download pypy 2.7: here and pypy 3.11: here
2. TO INSTALL PYPY 2.7 OR PYPY 3.11, UNZIP THE FILES INTO YOUR /home/username/opt folder, you may have to make the folder optionally, and then leave the window open. Now type “sudo apt install pluma kate git cmake make” this will get you some text editors and other programs you may be using. Now type this “sudo pluma /home/username/.bashrc” and at the bottom of the file you have to make variables for the various folders inside of the folder you just unzipped. That is, i’ll show you what my file looks like after you are completed, at least the interesting parts:

#------------------------------------------------------------------------------
# BEGIN GCC-16 (COMPILED BY YOU)
#------------------------------------------------------------------------------

USR_LOCAL="/usr/local"
GCC_BIN_DIR="$USR_LOCAL/bin"
GCC_LIB_DIR="$USR_LOCAL/include"
GCC_ETC="$USR_LOCAL/etc"
GCC_INC="$USR_LOCAL/include"
GCC_LIB="$USR_LOCAL/lib"
GCC_LIB64="$GCC_LIB:64"
GCC_LIBEXEC="$USR_LOCAL/libexec"
GCC_SBIN="$USR_LOCAL/sbin"
GCC_SRC="$USR_LOCAL/src"

GCC_ALL="$GCC_BIN_DIR:$GCC_LIB_DIR:$GCC_ETC:$GCC_INC:$GCC_LIB:$GCC_LIB64:$GCC_LIBEXEC:$GCC_SBIN:$GCC_SRC"

export PATH="$GCC_ALL:$PATH"
export LD_LIBRARY_PATH="$GCC_ALL:$LD_LIBRARY_PATH"
export LD_RUN_PATH="$GCC_ALL:$LD_RUN_PATH"

#------------------------------------------------------------------------------
# END GCC
#------------------------------------------------------------------------------

This is an example of what it takes to add GCC 16 to your system, and now when I type in just “gcc” at the terminal, gcc comes up. Same with PYPY, you have to make an item for each folder inside of the directory, but usually you don’t have to add subfolders, and then make a GCC_ALL variable, with variables being designated by the $ symbol, and declaration of variables is just VAR_NAME=”/dir/to/folder” then exporting the PATH variable that your system uses to find programs, you must also include the $PATH variable in the export command, so that you don’t lose your whole system. Supposedly this is like the more risky way of doing things, and there are other ways to add a program to a linux system, but this is the way that I use, because I have control over the code(tm) and I can control every aspect about how these programs are added to my system, instead of relying on linux to do it all for me. When you use the “sudo make install” command you would think it would do this, but it doesn’t, and you have to do it this way!

So anyways you don’t technically have to add anything to your system, and you can just type the full directory structure of the program each time you want to run it, but that’s just me I like to add the program to the system, thus it is kinda installed in a sense, for like when other programs or the system itself goes to run python3 code, it will use your PYPY interpreter you installed into the PATH variable.

So now we have a system with, well,

This post is continued in the post “Advanced Build Configurations” where we build clang from source, to have a completely up-to-date C or C++ compiler, with which you can do anything! Anything is possible in C and C++, even when you can’t, it always works, and there’s no downsides to C++ because it is so great that you cannot even judge it’s greatness, it is such a vast idea, and that is saying something when an idea is that big, anyways go learn to do a search on my website, and type in Advanced Build configurations” you’ll type it in lowercase I don’t know if it will come up or not, so here is the link to the post

the post “advanced build configurations” has been updated and now the cmake command works