Fernando de Oliveira wrote: > About the .a and .la. This is another thing I need to understand. Many > discussions, here.
.a files have it's contained functions embedded in the executable. It is only used in the link phase of the build process. If used, the executable does not look for the functions at run time. If a program uses a .a library and the library is updated, the program has to be relinked to use it. .la files are 'libtool archive' files. They are ascii and provide information for libtool to find libraries. If the .la file does not exist, the fallback is the default+specified library paths. Sometimes one .la file refers to another and, if missing, causes the build to fail. If all .la files are removed, then the build proceeds normally. AFAIK, the main capabilities that libtool provide is the ability to cross build from one architecture to another. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
