Feel free to drop your questions, suggestions or a simple “thank you” in the comment section. It is interesting how a seemingly small stuff like installing zlib could become a pain for two reasons: a different package name and the package name containing a “hidden” numeral one (1) which is confused with lowercase L. Note about linking C/C++ programs with zlib And if you would link against zlib in your program, add -lz to the gcc or g++ commands. For example, if you need the latest or a specific version of zlib which is not available in the distribution’s repository. However, I won’t recommend going the source code way just for installing zlib unless you have a good reason to do so. You may also download the source code of Zlib from its website and install it. Only install it if you require it otherwise you should be good with the main runtime zlib1g package. The other package, zlib1g-dev is development package. Many people make this mistake while typing the command. Learn also more about ELF then use readelf (& objdump) appropriately.Please keep in mind that the the letter before g is 1 (one), not lowercase L. ), make a small C example file some-example.c, then run gcc -S -fverbose-asm -O some-example.c and look into the produced some-example.s with an editor or pager. (you might later remove the -v option to gcc)Īlternatively, use the GNU as assembler syntax (not the nasm one), name your file file.S (if you want it to be preprocessed) or file.s (without preprocessing) and use gcc -v -Wall -m32 file.s -o myprog to compile it.īTW, to understand more about calling conventions, read the x86-64 ABI spec (and the similar one for 32 bits x86. Notice that you give to GCC an object file in ELF (for the linker invoked by gcc) which you previously produced with nasm. You should try linking with gcc -Wall -v -m32 file.o -o file asm as ELF object files by default, however file.asm is not an ELF object file).

s for assembler code, but probably handle unknown extensions like. S for preprocessable GNU assembler syntax, and. The second gcc command does not do what you wish.īut gcc does not know about *.asm file extensions (it knows about. Your first nasm command is probably creating a file.o file (and you should check that, e.g. The easiest way is to use ldd command which comes with glibc and in most cases it will print the same version as glibc: ldd version ldd (Ubuntu GLIBC 2.30-0ubuntu2.1) 2.30. Nasm -f elf file.asm gcc -m32 file.asm -o file I assembled and linked the program with the following commands :.

How to install glibc in ubuntu