-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Please send mails to an appropriate list, rather than a single developer]
According to Takis Psarogiannakopoulos on 7/15/2008 12:48 PM: | Hi there, | This may sound a bit naive but I am at a loss with the new autoconf | 2.62 scrips. First of all trying say to get 2.62 to work we are running to | the issue that loads of packages are compiled with previous versions (say 2.60 | etc etc) So is 2.62 backwards compatible? | IT SHOULD BE otherwise whats the point if the whole config needs to be | changed every time! You are correct that 2.62 is supposed to be backwards compatible (but read the NEWS file for details); in places where it is not, but where NEWS is silent, then please report that as a bug. There have already been some known regressions reported, such as with AC_C_BIGENDIAN, AC_USE_SYSTEM_EXTENSIONS, and AC_CONFIG_FILES($var_containing_newline), that we hope to have repaired for 2.63. | Also I am trying to modify the new automake 1.10.1 and find that | whenever I want to add say a AC_CHECK_HEADER([sys/sem.h]) inside its | configure.ac the autoconf 2.62 generates | an error about _AM_DEPENDENSIES(CC) ? What is this all about? Please post a sample configure.ac that reproduces this error. | | I would be greatful if you could enlighten me on these, I want to make a | GNU toolkit for EMC's SMP Unix and used to know very well autoconf, | automake, libtool. Now I cannot even add a simple AC_PROG_CC on | automake's configure.ac without getting the _AM_DEPENDENCIES error and | something about m4_pattern_allow? | | | Regards, | - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh9OHQACgkQ84KuGfSFAYCVAACaApw149s9x/C2OGnKArEoCmwe FwcAn2BIZ5++z1SEpv/fVlRf61YNKubc =eLWN -----END PGP SIGNATURE-----
