libc 4, a.out - DAIICT Intranet

More documents

Recommendations

Info

The first error is easy. I'll simply change AC_CONFIG_HEADER to AM_CONFIG_HEADER in "configure.ac". Automake is just telling you here it prefers its version of the macro instead of Autoconf's version: Listing of "configure.ac": ... #AC_CONFIG_HEADER([config.h]) AM_CONFIG_HEADER([config.h])
As for the errors ab<strong>out</strong> PACKAGE and VERSION, this information can be added to "configure.ac" in several ways. The best way here is to add AM_INIT_AUTOMAKE(hello, 1.0) here, right after AC_INIT(...): Listing of "configure.ac": ... AC_INIT(FULL-PACKAGE-NAME, VERSION, BUG-REPORT- ADDRESS) AM_INIT_AUTOMAKE(hello, 1.0) ... But in fact, this is one of the few standard macros you should know when you use Automake. The first argument to the AM_INIT_AUTOMAKE is the name of the package, and the second argument is the version of the package.
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 and 16: ●But we don't have "config.h" yet
Page 17 and 18: Notice how "autoheader" generates "
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: Dealing with errors Now, let's run
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?