The -l option in gcc

Question

I have just began reading the book: Advanced Programming in Unix Enviornment and try to compile the first example code, just the same as in this thread. Although the problem

Answer 1

This is documented in §2.13 "Options for Linking" in the GCC manual:

-llibrary

Search the library named library when linking.

It makes a difference where in the command you write this option; the linker searches processes libraries and object files in the order they are specified. Thus, `foo.o -lz bar.o' searches library `z' after file `foo.o' but before `bar.o'. If `bar.o' refers to functions in `z', those functions may not be loaded.

The linker searches a standard list of directories for the library, which is actually a file named `liblibrary.a'. The linker then uses this file as if it had been specified precisely by name.

The directories searched include several standard system directories plus any that you specify with `-L'.

Normally the files found this way are library files--archive files whose members are object files. The linker handles an archive file by scanning through it for members which define symbols that have so far been referenced but not defined. But if the file that is found is an ordinary object file, it is linked in the usual fashion. The only difference between using an `-l' option and specifying a file name is that `-l' surrounds library with `lib' and `.a' and searches several directories.

Answer 2

The -l option tells gcc to link in the specified library. In this case the library is apue, that it happens to line up with the name of a header file is just how the apue coders designed their project. In reality the -l option has nothing to do with header files. Like cas says in the comments, read the manpage, it'll give you much more information.