libc 4, a.out - DAIICT Intranet

More documents

Recommendations

Info

$ ./configure checking for gcc... gcc checking for C compiler default <strong>out</strong>put... a.<strong>out</strong> checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes configure: creating ./config.status config.status: creating Makefile config.status: creating config.h $ ls Makefile autoscan.log config.log configure.ac Makefile.in config.h config.status* hello* autom4te.cache/ config.h.in configure* hello.c $
Notice how "autoheader" generates "config.h.in", then "config.h.in" was used by "configure" to generate "config.h"? In general, that's how Autoconf works: We use some program to generate ".in", and ".in" will be used by Autoconf to generate "".
Page 1 and 2: Linux Library Handling The possible
Page 3 and 4: How to compile programs with Autoto
Page 5 and 6: Autotools is a collection of three
Page 7 and 8: Listing of "Makefile" # Makefile: A
Page 9 and 10: Let's add Autoconf First, we create
Page 11 and 12: $ mv Makefile Makefile.in $ ls Make
Page 13 and 14: Let's review what we've done so far
Page 15: ●But we don't have "config.h" yet
Page 19 and 20: ●config.h : There are some consta
Page 21 and 22: $ autoscan Use of uninitialized val
Page 23 and 24: Notice a few things here: ● After
Page 25 and 26: * Define to 1 if you have the head
Page 27 and 28: Using this header file, we can chec
Page 29 and 30: A separate function to handle the t
Page 31 and 32: What is Automake? Automake is a pro
Page 33 and 34: Here's the "Makefile.am" we'll be u
Page 35 and 36: Dealing with errors Now, let's run
Page 37 and 38: As for the errors about PACKAGE and
Page 39 and 40: So, here is how we can use Automake

libc 4, a.out - DAIICT Intranet

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?