-
Notifications
You must be signed in to change notification settings - Fork 23
/
NEWS
2848 lines (2119 loc) · 112 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
GNU Autoconf NEWS - User visible changes.
* Noteworthy changes in release ?.? (????-??-??) [?]
** Backward incompatibilities
*** AC_PROG_CC now prefers C23 if available.
Older code may need to be updated, as C23 has removed old-style
(K&R) function definitions and declarations, and has new keywords
alignas, alignof, bool, constexpr, false, nullptr, static_assert,
thread_local, typeof, typeof_unqual, true.
*** AC_PROG_CC no longer checks __STDC__ or variable length arrays (VLAs).
This ports better to MSVC, which does not define __STDC__ and does
not support VLAs. Although C99 requires VLAs, they are optional in
C11 and later. Programs can use AC_C_VARARRAYS and __STDC_NO_VLA__
to use VLAs if available.
*** AC_PROG_CXX no longer attempts to switch to C++98 or C++11.
Instead, it uses the compiler's default, which you can override
by configuring with something like CXX='g++ -std=gnu++11'.
This reverts to Autoconf 2.69 behavior, and also fixes a bug where
AC_PROG_CXX rejected C++20 compilers.
** New features
*** Programs now recognize #elifdef and #elifndef.
The autom4te, autoscan and ifnames programs now recognize the two
preprocessor directives, which were introduced in C23 and C++23.
** Notable bug fixes
*** AC_FUNC_STRNLEN now detects Android 5.0's broken strnlen.
*** AC_PROG_OBJC now finds the GNU Objective-C compiler, as packaged in
EPEL 9, by default, without the user having to set the OBJC variable.
*** Autoconf no longer generates ${1+"$@"} in scripts, working around
a bug in AIX 7.2 ksh93.
* Noteworthy changes in release 2.72 (2023-12-22) [release]
** Backward incompatibilities
*** Configure scripts no longer support pre-1989 C compilers.
Specifically, compilers that *only* implement the original “K&R”
function definition syntax, and not the newer “prototyped” syntax,
will not be able to parse the test programs now emitted by
AC_CHECK_FUNC, AC_LANG_CALL, and similar macros. AC_PROG_CC still
accepts such compilers, but this may change in the near future.
This change was necessary in order to support the upcoming 2024
edition of the C standard (often referred to as “C23”), which will
officially remove the function declaration syntax used by
AC_CHECK_FUNC in Autoconf 2.71 and earlier. We feel that support
for compilers that support only C 2024 is more useful, nowadays,
than support for compilers that don’t implement a core feature of
C 1989.
*** Autoconf developers now need Perl 5.10 (2007) or later.
“Autoconf developers” means specifically people hacking on Autoconf
itself. Autoconf *users*, i.e. authors of configure.ac files and
add-on M4 macros, still need only Perl 5.6 (2000) or later.
We do recommend all Autoconf users upgrade to Perl 5.10 or later if
possible, as this version significantly improves Perl’s ability to
handle files with last-modification timestamps separated by less
than a second. (Note: even in the most recent release, Perl cannot
always match the file system’s timestamp resolution.)
Generated configure scripts continue to run without Perl.
*** Autoconf users now need GNU M4 1.4.8 (2006) or later.
Use of GNU M4 1.4.16 or later is recommended, as all earlier versions
are known to have had serious bugs in the text-processing builtins
on some, but not all, operating systems. Autoconf’s own configure
script will attempt to find a version of M4 that is not affected by
these bugs.
Note: Autoconf 2.70 and 2.71 include code that malfunctions with
M4 1.4.6 or 1.4.7. However, the only effect of the malfunction is
that you will get a confusing error message if you run autoconf on
a configure.ac that neglects to use AC_INIT or AC_OUTPUT.
Generated 'configure' scripts continue to run without M4.
*** Some m4sh diversions have been renumbered.
This will only affect macros that use m4_divert with numbered rather
than named diversions, which has always been strongly discouraged
both by the documentation and with warnings.
*** AC_FUNC_GETGROUPS and AC_TYPE_GETGROUPS no longer run test programs.
These macros were testing for OS bugs that we believe are at least
twenty years in the past. Most operating systems are now trusted to
provide an accurate prototype for getgroups in unistd.h, and to
implement it as specified in POSIX.
AC_FUNC_GETGROUPS still includes a short block-list of OSes with
known, severe bugs in getgroups. It can be overridden using
config.site. If you encounter a mistake in this list,
please report it to bug-autoconf.
*** All internal uses of AC_EGREP_CPP and AC_EGREP_HEADER have been removed.
These macros look for text matching a regular expression in the
output of the C preprocessor. Their use has been discouraged for
many years, as they tend to be unreliable; it is better to find a
way to use AC_COMPILE_IFELSE or AC_PREPROC_IFELSE instead. We have
finally taken our own advice.
This change might break configure scripts that expected probes for
‘grep’ and/or the C preprocessor to happen as a side effect of an
unrelated operation. Such scripts can be fixed by adding
AC_PROG_EGREP and/or AC_PROG_CPP in an appropriate place.
The macros affected by this change are AC_C_STRINGIZE,
AC_C_VARARRAYS, AC_FUNC_GETGROUPS, AC_FUNC_GETLOADAVG,
AC_HEADER_TIOCGWINSZ, AC_PROG_GCC_TRADITIONAL, AC_TYPE_GETGROUPS,
AC_TYPE_UID_T, and AC_XENIX_DIR. Many of these macros are themselves
obsolete; if your configure script uses any of them, check whether
it is actually needed.
** New features
*** Support for ensuring time_t is Y2038-safe
configure can now ensure that time_t can represent moments in time
after 18 January 2038, i.e. 2**31 - 1 seconds after the Unix epoch.
On most “64-bit” systems this is true by default; the new feature
is detection of systems where time_t is a 32-bit signed integer by
default, *and* there is an alternative mode in which it is larger,
in which case that mode will be enabled.
In this release, all configure scripts that use AC_SYS_LARGEFILE
gain a new command line option --enable-year2038. When this option
is used, the configure script will check for and enable support for
a large time_t.
This release also adds two new macros, AC_SYS_YEAR2038 and
AC_SYS_YEAR2038_RECOMMENDED. Both have all the effects of
AC_SYS_LARGEFILE. (This is because it is not possible to enlarge
time_t without also enlarging off_t, on any system we are aware of.)
AC_SYS_YEAR2038 additionally flips the default for --enable-year2038;
a configure script that uses this macro will check for and enable
support for a large time_t by default, but this can be turned off by
using --disable-year2038. AC_SYS_YEAR2038_RECOMMENDED goes even
further, and makes the configure script fail on systems that do not
seem to support timestamps after 18 January 2038 at all. This
failure can be suppressed by using --disable-year2038.
Changing the size of time_t can change a library’s ABI. Therefore,
application and library builders should take care that all packages
are configured with consistent use of --enable-year2038 or
--disable-year2038, to ensure binary compatibility. This is similar
to longstanding consistency requirements with --enable-largefile and
--disable-largefile.
In this release, these macros only know how to enlarge time_t on two
classes of systems: 32-bit MinGW, and any system where time_t can be
enlarged by defining the preprocessor macro _TIME_BITS with the
value 64. At the time this NEWS entry was written, only GNU libc
(version 2.34 and later) supported the latter macro. Authors of
other C libraries with a 32-bit time_t are encouraged to adopt
_TIME_BITS, rather than inventing a different way to enlarge time_t.
*** AC_USE_SYSTEM_EXTENSIONS now enables C23 Annex F extensions
by defining __STDC_WANT_IEC_60559_EXT__.
** Obsolete features and new warnings
*** Autoconf now quotes 'like this' instead of `like this'.
Autoconf’s diagnostics now follow current GNU coding standards,
which say that diagnostics in the C locale should quote 'like this'
with plain apostrophes instead of the older GNU style `like this'
with grave accent and apostrophe.
*** AC_PROG_GCC_TRADITIONAL no longer does anything.
This macro has had no useful effect since GCC dropped support for
traditional-mode compilation in version 3.3 (released in 2003), and
the systems that needed it are also long obsolete. It is now a
compatibility synonym for AC_PROG_CC.
** Notable bug fixes
*** autom4te now uses fine-grained file timestamps
Autoconf’s internal “autom4te” utility is now able to compare file
modification timestamps with sub-second precision, when available.
This eliminates a class of bugs where autom4te fails to regenerate
an outdated file. Automake 1.17 (forthcoming) is required for a
complete fix.
*** AC_HEADER_STDBOOL, AC_CHECK_HEADER_STDBOOL are obsolescent and less picky.
These macros are now obsolescent, as most programs can simply include
stdbool.h unconditionally. If you use these macros, they now accept
a stdbool.h that exists but does nothing, so long as ‘bool’, ‘true’,
and ‘false’ work anyway. This is for compatibility with C23 and
with C++.
*** AC_PROG_MKDIR_P now falls back on plain 'mkdir -p'.
When AC_PROG_MKDIR_P cannot find a mkdir implementation that is
known to lack race condition bugs, it now falls back on 'mkdir -p'
instead of falling back on a relative path to install-sh, as the
relative paths now seem to be a more important problem than the
problems of ancient mkdir implementations with race condition bugs.
See <https://savannah.gnu.org/support/?110740>. The only ancient
mkdir still supported is Solaris 10 /usr/bin/mkdir, and for that
platform AC_PROG_MKDIR_P falls back on /opt/sfw/bin/mkdir which
should work if it is installed; if not, you should avoid parallel
'make' on that platform.
*** Better diagnostics for calling m4_warn() with a bad first argument
Calling m4_warn with a first argument that doesn’t match any of the
official warning categories now produces a sensible error message,
instead of something that makes it look like there’s a bug in the
guts of autom4te. Also, the documentation has been adjusted in
several places to make it clearer what the official warning
categories are.
Note: In Autoconf 2.69 and earlier, the manual said that [] and [all]
could be used as the first argument to m4_warn. This was incorrect,
even at the time.
*** Improved compatibility with a wide variety of systems and tools
including CheriBSD, Darwin (macOS), GNU Guix, OS/2, z/OS, Bash 5.2,
the BusyBox shell and utilities, Clang/LLVM version 16, the upcoming
GCC version 14, etc.
** Known bugs
*** AC_SYS_LARGEFILE and AC_SYS_YEAR2038 only work correctly in C mode.
This is only a problem for configure scripts that invoke either
macro while AC_LANG([something other than C]) is in effect, and
will only be a *visible* problem on systems where support
for large files and/or timestamps after 2038 are *available*
but not enabled by default.
This is the cause of the AC_SYS_LARGEFILE, AC_SYS_YEAR2038, and/or
AC_SYS_YEAR2038_RECOMMENDED testsuite failures on some systems.
See <https://savannah.gnu.org/support/index.php?110983> for details
and a workaround.
* Noteworthy changes in release 2.71 (2021-01-28) [stable]
** Bug fixes, including:
*** Compilers that support C99 but not C2011 are detected correctly.
*** Compatibility improved with clang and Oracle C++.
*** Compatibility restored with automake's rules for regenerating configure.
*** Compatibility restored with old versions of std-gnu11.m4.
Packages that wish to maintain compatibility with Autoconf 2.69 or
older, should update their copy of std-gnu11.m4 from Gnulib as soon
as practical, as the compatibility code bulks up the configure script.
Packages that require Autoconf 2.70 can drop this file entirely.
* Noteworthy changes in release 2.70 (2020-12-08) [stable]
** Backward incompatibilities:
*** Warnings about obsolete constructs are now on by default.
These warnings can be turned off with ‘-Wno-obsolete’.
Many of these warnings advise maintainers to run autoupdate.
Be aware that autoupdate cannot solve all backward compatibility
problems, and cannot completely solve all of the problems it does
address. A configure script edited by autoupdate is likely to
need further manual fix-ups.
*** Many macros have become pickier about argument quotation.
If you get a shell syntax error from your generated configure
script, or seemingly impossible misbehavior (e.g. entire blocks of
the configure script not getting executed), check first that all
macro arguments are properly quoted. The “M4 Quotation” section of
the manual explains how to quote macro arguments properly.
It is unfortunately not possible for autoupdate to correct
quotation errors.
*** Many macros no longer AC_REQUIRE as many other macros as they used to.
This can expose several classes of latent bugs. These are the ones
we know about:
- Make sure to explicitly invoke all of the macros that set result
variables used later in the configure script, or in generated
Makefiles.
- Autoconf macros that use AC_REQUIRE are not safe to use in shell
control-flow constructs that appear outside of macros defined by
AC_DEFUN. Use AS_IF, AS_CASE, etc. instead. (See the
“Prerequisite Macros” section of the manual for details.)
The set of macros that use AC_REQUIRE internally may change from
release to release. The only macros that are guaranteed *not* to
use AC_REQUIRE are the macros for acting on the results of a
test: AC_DEFINE, AC_SUBST, AC_MSG_*, AC_CACHE_CHECK, etc.
- AC_REQUIRE cannot be applied to macros that need to be used with
arguments. Instead, invoke the macro normally, with its arguments.
*** More macros use config.sub and config.guess internally.
As a consequence of improved support for cross compilation (see below),
more macros now use the auxiliary scripts ‘config.sub’ and ‘config.guess’.
If you use any of the affected macros, these scripts must be available
when your configure script is run, even if you have no intention of
ever cross-compiling your program.
autoreconf will issue an error if any auxiliary scripts are needed but
cannot be found. (It is not currently possible to make autoconf
itself issue this error.)
‘autoreconf --install’ will add ‘config.sub’, ‘config.guess’, and
‘install-sh’ to your source tree if they are needed. If you are
using Automake, scripts added to your tree by ‘autoreconf --install’
will automatically be included in the tarball produced by ‘make dist’;
otherwise, you will need to arrange for them to be distributed
yourself.
See the “Input” section of the manual for more detail, including
where to get the auxiliary scripts that may be needed by autoconf macros.
*** Setting CC to a C++ compiler is no longer supported.
The C and C++ languages have diverged enough that we can no longer
guarantee that test C programs will be processed as intended by a
C++ compiler. In this release, configure will proceed anyway, but
many test results will be incorrect. In a future release, we may
make AC_PROG_CC error out if it detects that CC is a C++ compiler.
See the “Language Choice” section of the manual for instructions on
how to write configure scripts for C++ programs, and for programs
with code in more than one language.
*** Running configure tests with warnings promoted to errors is not supported.
For instance, setting ‘CC="gcc -Werror"’ on the configure command
line, or adding -Werror to CFLAGS early in the configure script when
the compiler recognizes this option, is very likely to cause
subsequent tests to fail.
This has never been guaranteed to work; the code generated by
AC_CHECK_FUNC, for instance, is incorrect by a strict reading of the
original 1989 C standard, and has been ever since that macro was
introduced. Problems are more likely with newer, pickier compilers.
To enable compiler warnings and/or warnings-as-errors mode for your
own code, we currently recommend a dedicated Makefile variable
(e.g. ‘WARN_CFLAGS’) that is set by AC_SUBST when appropriate.
The Gnulib ‘warnings’ and ‘manywarnings’ modules can help with this.
We plan to add core support for probing for useful sets of compiler
warnings in a future release.
*** Including confdefs.h manually may cause test failures.
This has never been necessary; confdefs.h is automatically included
at the beginning of all test programs (by AC_LANG_SOURCE). Because
of the way confdefs.h is generated and used, it is not practical to
give it a multiple inclusion guard. Therefore, if you include it
yourself, all of its definitions will be scanned twice.
Historically this has not been a problem, because confdefs.h only
makes macro definitions, and the C standard allows redefinitions
of macros as long as they’re exactly the same, but newer, pickier
compilers may complain anyway (see for instance GCC bug 97998).
*** Older versions of automake and aclocal (< 1.8) are no longer supported.
*** AC_CONFIG_SUBDIRS no longer directly supports Cygnus configure.
If you are still using an Autoconf script to drive configuration of
a multi-package build tree where some subdirectories use Cygnus
configure, copy or link $ac_aux_dir/configure into each subdirectory
where it is needed. Please also contact us; we were under the
impression nobody used this very old tool anymore.
*** AC_CHECK_HEADER and AC_CHECK_HEADERS only do a compilation test.
This completes the transition from preprocessor-based header tests
begun in Autoconf 2.56.
The double test that was the default since Autoconf 2.64 is no
longer available. You can still request a preprocessor-only test
by specifying [-] as the fourth argument to either macro, but this
is now deprecated. If you really need that behavior use
AC_PREPROC_IFELSE.
*** AC_INCLUDES_DEFAULT assumes an ISO C90 compliant C implementation.
Specifically, it assumes that the ISO C90 header <stddef.h>
is available, without checking for it, and it does not include
the pre-standard header <memory.h> at all. If the POSIX header
<strings.h> exists, it will be included, without first testing
whether both <string.h> and <strings.h> can be included in the
same source file.
AC_INCLUDES_DEFAULT still checks for the existence of <stdlib.h>,
<string.h>, and <stdio.h>, because these headers may not exist
in a “freestanding environment” (a compilation mode intended for OS
kernels and similar, where most of the features of the C library are
optional). Most programs need not use ‘#ifdef HAVE_STDLIB_H’ etc in
their own code.
For compatibility’s sake, the C preprocessor macro STDC_HEADERS
will be defined when both <stdlib.h> and <string.h> are available;
however, <stdarg.h> and <float.h> are no longer checked for
(these, like <stddef.h>, are required to exist in a freestanding
environment). New code should not refer to this macro.
Future releases of Autoconf may reduce the set of headers checked
for by AC_INCLUDES_DEFAULT.
*** AS_ECHO and AS_ECHO_N unconditionally use ‘printf’.
This is substantially simpler, more reliable, and, in most cases,
faster than attempting to use ‘echo’ at all. However, if ‘printf’
is not a shell builtin, configure scripts will run noticeably
slower, and if ‘printf’ is not available at all, they will crash.
The only systems where this is known to be a problem are extremely
old, and unlikely to be able to handle modern C programs for other
reasons (e.g. not having a C90-compliant compiler at all).
*** Configure scripts require support for $( ... ) command substitution.
This POSIX shell feature is approximately the same age as
user-defined functions, but there do exist shells that support
functions and not $( ... ), such as Solaris 10 /bin/sh.
Configure scripts will automatically locate a shell that supports
this feature and re-execute themselves with it, if necessary, so
the new requirement should be transparent to most users.
In this release, most of Autoconf’s code still uses the older `...`
notation for command substitution.
*** AC_INIT now trims extra white space from its arguments.
For instance, AC_INIT([ GNU Hello ], [1.0]) will set PACKAGE_NAME
to “GNU Hello”.
*** Macros that take whitespace-separated lists as arguments
now always expand macros within those arguments.
Formerly, these macros would *usually* expand those arguments, but
the behavior was not reliable nor was it consistent between autoconf
and autoheader.
Macro expansion within these arguments is deprecated; if expansion
changes the list, a warning in the “obsolete” category will be
emitted. Note that ‘dnl’ is a macro. Putting ‘dnl’ comments inside
any argument to an Autoconf macro is, in general, only supported
when that argument takes more Autoconf code (e.g. the ACTION-IF-TRUE
argument to AC_COMPILE_IFELSE).
The affected macros are AC_CHECK_FILES, AC_CHECK_FUNCS,
AC_CHECK_FUNCS_ONCE, AC_CHECK_HEADERS, AC_CHECK_HEADERS_ONCE,
AC_CONFIG_MACRO_DIRS, AC_CONFIG_SUBDIRS, and AC_REPLACE_FUNCS.
*** AC_FUNC_VFORK no longer ignores a signal-handling bug in Solaris 2.4.
This bug was being ignored because Emacs wanted to use ‘vfork’ on
Solaris 2.4 anyway, but current versions of Emacs have dropped
support for Solaris 2.4. Most programs will want to avoid ‘vfork’
on this OS because of this bug.
*** AC_FUNC_STRERROR_R assumes strerror_r is unavailable if it’s not declared.
The fallback technique it used to probe strerror_r’s return type
when the function was present in the C library, but not declared by
<string.h>, was fragile and did not work at all when cross-compiling.
The systems where this fallback was necessary were all obsolete.
Programs that use AC_FUNC_STRERROR_R should make sure to test the
preprocessor macro HAVE_DECL_STRERROR_R before using strerror_r at all.
*** AC_OPENMP can’t be used if you have files named ‘mp’ or ‘penmp’.
Autoconf will now issue an error if AC_OPENMP is used in a configure
script that’s in the same directory as a file named ‘mp’ or ‘penmp’.
Configure scripts that use AC_OPENMP will now error out upon
encountering files with these names in their working directory
(e.g. when the build directory is separate from the source directory).
If you have files with these names at the top level of your source
tree, we recommend either renaming them or moving them into a
subdirectory. See the documentation of AC_OPENMP for further
explanation.
** New features
*** Configure scripts now support a ‘--runstatedir’ option.
This defaults to ‘${localstatedir}/run’. It can be used, for
instance, to place per-process temporary runtime files (such as pid
files) into ‘/run’ instead of ‘/var/run’.
*** autoreconf will now run gtkdocize and intltoolize when appropriate.
*** autoreconf now recognizes AM_GNU_GETTEXT_REQUIRE_VERSION.
This macro can be used with gettext 0.19.6 or later to specify
a *minimum* version requirement for gettext, instead of the *fixed*
version requirement specified by AM_GNU_GETTEXT_VERSION.
*** autoheader handles secondary config headers better.
It is no longer necessary to duplicate AC_DEFINE templates in the
main configuration header for autoheader to notice them.
*** AC_PROG_CC now enables C2011 mode if the compiler supports it.
If not, it will fall back to C99 and C89, as before. Similarly,
AC_PROG_CXX now enables C++2011 if available, falling back on C++98.
*** New macro AC_C__GENERIC tests for C2011 _Generic support.
*** AC_C_VARARRAYS has been aligned with C2011.
It now defines __STDC_NO_VLA__ if variable-length arrays are not
supported but the compiler does not define __STDC_NO_VLA__.
For backward compatibility with Autoconf 2.61-2.69 AC_C_VARARRAYS
still defines HAVE_C_VARARRAYS, but this result macro is obsolescent.
*** New macro AC_CONFIG_MACRO_DIRS.
This macro can be used more than once and accepts a list of
directories to search for local M4 macros. With Automake 1.13 and
later, use of this macro eliminates a reason to use ACLOCAL_AMFLAGS
in Makefile.am.
The older AC_CONFIG_MACRO_DIR, which could only be used once, is
still supported but considered deprecated.
*** AC_USE_SYSTEM_EXTENSIONS knows about more extensions to enable.
System extensions will now be enabled on HP-UX, macOS, and MINIX.
Optional ISO C library components (e.g. decimal floating point) will
also be enabled.
*** New compatibility macro AC_CHECK_INCLUDES_DEFAULT.
This macro runs the checks normally performed as a side-effect by
AC_INCLUDES_DEFAULT, if they haven’t already been done. Autoupdate
will replace certain obsolete constructs, whose only remaining
useful effect is to trigger those checks, with this macro. It is
unlikely to be useful otherwise.
*** AC_REQUIRE_AUX_FILE has been improved.
Configure scripts now check, on startup, for the availability of all
the aux files that were mentioned in an AC_REQUIRE_AUX_FILE
invocation. This should help prevent certain classes of packaging
errors.
Also, it is no longer necessary for third-party macros that use
AC_REQUIRE_AUX_FILE to mention AC_CONFIG_AUX_DIR_DEFAULT. However,
if you are using AC_CONFIG_AUX_DIR_DEFAULT *without* also using
AC_REQUIRE_AUX_FILE, please start using AC_REQUIRE_AUX_FILE to
specify the aux files you actually need, so that the check can be
effective.
*** AC_PROG_LEX has an option to not look for yywrap.
AC_PROG_LEX now takes one argument, which may be either ‘yywrap’ or
‘noyywrap’. If it is ‘noyywrap’, AC_PROG_LEX will only set LEXLIB
to ‘-lfl’ or ‘-ll’ if a scanner that defines both main and yywrap
itself still needs something else from that library. On the other
hand, if it is ‘yywrap’, AC_PROG_LEX will fail (setting LEX to ‘:’
and LEXLIB to nothing) if it can’t find a library that defines yywrap.
In the absence of arguments, AC_PROG_LEX’s behavior is bug-compatible
with 2.69, which did neither of the above things (see the manual for
details). This mode is deprecated.
We encourage all programs that use AC_PROG_LEX to use the new
‘noyywrap’ mode, and to define yywrap themselves, or use %noyywrap.
The yywrap function in lib(f)l is trivial, and self-contained
scanners are easier to work with.
** Obsolete features and new warnings
*** Use of the long-deprecated name ‘configure.in’ for the autoconf
input file now elicits a warning in the “obsolete” category.
*** Use of the undocumented internal shell variables $as_echo and
$as_echo_n now elicits a warning in the “obsolete” category.
The macros AS_ECHO and AS_ECHO_N should be used instead.
*** autoconf will now issue warnings (in the “syntax” category)
if the input file is missing a call to AC_INIT and/or AC_OUTPUT.
*** autoconf will now issue warnings (in the “syntax” category)
for a non-literal URL argument to AC_INIT, and for a TARNAME
argument to AC_INIT which is either non-literal or contains
characters that should not be used in file names (e.g. ‘*’).
*** AC_PROG_CC_STDC, AC_PROG_CC_C89, AC_PROG_CC_C99 are now obsolete.
Applications should use AC_PROG_CC.
*** AC_HEADER_STDC and AC_HEADER_TIME are now stubs.
They still define the C preprocessor macros STDC_HEADERS and
TIME_WITH_SYS_TIME, respectively, but they no longer check for the
ancient, non-ISO-C90 compliant systems where formerly those macros
would not be defined. Autoupdate will remove them.
These macros were already labeled obsolete in the manual.
*** AC_DIAGNOSE, AC_FATAL, AC_WARNING, and _AC_COMPUTE_INT are now
replaced with modern equivalents by autoupdate.
These macros were already labeled obsolete in the manual.
*** AC_CONFIG_HEADER is now diagnosed as obsolete, and replaced with
AC_CONFIG_HEADERS by autoupdate.
This macro has been considered obsolete for many years and was not
documented at all.
*** The macro AC_OBSOLETE is obsolete.
Autoupdate will replace it with m4_warn([obsolete], [explanation]).
If possible, macros using AC_OBSOLETE should be converted to use
AU_DEFUN or AU_ALIAS instead, which enables autoupdate to replace
them, but this has to be done by hand and is not always possible.
This macro has been considered obsolete for many years, but was not
officially declared as such.
*** Man pages for config.guess and config.sub are no longer provided.
They were moved to the master source tree for config.guess and
config.sub.
** Notable bug fixes
*** Compatible with current Automake, Libtool, Perl, Texinfo, and shells.
All of autoconf’s tools and generated scripts, and the build process
and testsuite for autoconf itself, have been tested to work
correctly with current versions of Automake, Libtool, Perl, Texinfo,
bash, ksh93, zsh, and FreeBSD and NetBSD /bin/sh.
Generated configure scripts are expected to work reliably with an
even wider variety of shells, including BusyBox sh and various
proprietary Unixes’ /bin/sh, as long as they are minimally compliant
with the Unix95 shell specification. Notably, support for
shell-script functions and the ‘printf’ builtin are required.
*** Checks compatible with current language standards and compilers.
Many individual macros have been improved to accommodate changes in
recent versions of the C and C++ language standards, and new
features and quirks of commonly used compilers (both free and
proprietary).
*** Improved support for cross compilation.
Many individual macros have been improved to produce more accurate
results when cross-compiling.
*** Improved robustness against unusual build environments.
Many bugs have been fixed where generated configure scripts would
fail catastrophically under unusual conditions, such as stdout being
closed, or $TMPDIR not being an absolute path, or the root directory
being mentioned in $PATH.
*** AC_CHECK_FUNCS_ONCE and AC_CHECK_HEADERS_ONCE now support multiple
programming languages. They no longer perform all checks in the
language active upon the first use of the macro.
*** AC_CHECK_DECL and AC_CHECK_DECLS will now detect missing declarations for
library functions that are also Clang compiler builtins.
*** AC_PATH_X and AC_PATH_XTRA don’t search for X11 when cross-compiling.
Libraries and headers found by running xmkmf or searching /usr/X11,
/usr/X11R7, etc. are likely to belong to a native X11 installation
for the build machine and to be inappropriate for cross compilation.
To cross-compile programs that require X11, we recommend putting the
headers and libraries for the host system in your cross-compiler’s
default search paths. Alternatively, use configure’s --x-includes
and --x-libraries command line options to tell it where they are.
*** AS_IF’s if-false argument may be empty after macro expansion.
This long-standing limitation broke configure scripts that used
macros in this position that emitted shell code in 2.69 but no
longer do, so we have lifted it.
*** AC_HEADER_MAJOR detects the location of the major, minor, and
makedev macros correctly under glibc 2.25 and later.
*** AC_FC_LINE_LENGTH now documents the maximum portable length of
“unlimited” Fortran source code lines to be 250 columns, not 254.
*** AC_INIT and AS_INIT no longer embed (part of) the path to the
source directory in generated files.
We believe this was the only case where generated file contents
could change depending on the environment outside the source tree
itself. If you find any other cases please report them as bugs.
*** config.log properly escapes arguments in the header comment.
*** config.status --config output is now quoted in a more readable fashion.
** Autotest enhancements
*** Autotest provides a new macro AT_DATA_UNQUOTED, similar to AT_DATA
but processing variable substitutions, command substitutions and
backslashes in the contents argument.
*** AC_CONFIG_TESTDIR will automatically pass EXEEXT to a testsuite (via
the atconfig file).
*** AT_TESTED arguments can use variable or command substitutions, including
in particular $EXEEXT
*** New macros AT_PREPARE_TESTS, AT_PREPARE_EACH_TEST, and AT_TEST_HELPER_FN.
These provide an official way to define testsuite-specific
initialization code and shell functions.
* Noteworthy changes in release 2.69 (2012-04-24) [stable]
** Autoconf now requires perl 5.6 or better (but generated configure
scripts continue to run without perl).
* Noteworthy changes in release 2.68b (2012-03-01) [beta]
Released by Eric Blake, based on git versions 2.68.*.
** Autoconf-generated configure scripts now unconditionally re-execute
themselves with $CONFIG_SHELL, if that's set in the environment.
** The texinfo documentation no longer specifies "front-cover" or
"back-cover" texts, so that it may now be included in Debian's
"main" section.
** Support for the Go programming language has been added. The new macro
AC_LANG_GO sets variables GOC and GOFLAGS.
** AS_LITERAL_IF again treats '=' as a literal. Regression introduced in
2.66.
** The macro AS_EXECUTABLE_P, present since 2.50, is now documented.
** Macros
- AC_PROG_LN_S and AS_LN_S now fall back on 'cp -pR' (not 'cp -p') if 'ln -s'
does not work. This works better for symlinks to directories.
- New macro AC_HEADER_CHECK_STDBOOL.
- New and updated macros for Fortran support:
AC_FC_CHECK_BOUNDS to enable array bounds checking
AC_F77_IMPLICIT_NONE and AC_FC_IMPLICIT_NONE to disable implicit integer
AC_FC_MODULE_EXTENSION to compute the Fortran 90 module name extension
AC_FC_MODULE_FLAG for the Fortran 90 module search path flag
AC_FC_MODULE_OUTPUT_FLAG for the Fortran 90 module output directory flag
AC_FC_PP_SRCEXT for preprocessed Fortran source files extensions
AC_FC_PP_DEFINE for the Fortran preprocessor define flag
* Noteworthy changes in release 2.68 (2010-09-22) [stable]
Released by Eric Blake, based on git versions 2.67.*.
** AC_MSG_ERROR (and AS_ERROR) can once again be followed immediately by
'dnl'. Regression introduced in 2.66.
** AC_INIT again allows URLs with '?' for its BUG-REPORT argument.
Regression introduced in 2.66.
** AC_REPLACE_FUNCS again allows a non-literal argument, such as a shell
variable that expands to a list of functions to check. Regression
introduced in 2.66.
** AT_BANNER() with empty argument will cause visual separation from previous
test category.
** The macros AC_PREPROC_IFELSE, AC_COMPILE_IFELSE, AC_LINK_IFELSE, and
AC_RUN_IFELSE now warn if the first argument failed to use
AC_LANG_SOURCE or AC_LANG_PROGRAM to generate the conftest file
contents. A new macro AC_LANG_DEFINES_PROVIDED exists if you have
a compelling reason why you cannot use AC_LANG_SOURCE but must
avoid the warning.
** The macro m4_define_default is now documented.
** Symlinked config.cache files are supported; configure now tries to
update non-symlinked cache files atomically, so that concurrent configure
runs do not leave behind broken cache files. It is still unspecified
which subset or union of results is cached though.
** Autotest testsuites should not contain long text lines any more, and be
portable even when very many test groups are used.
** AT_CHECK semantics with respect to the Autotest variable $at_status and
shell execution environment of the arguments are documented now.
** AC_FC_LIBRARY_LDFLAGS now tolerates output from newer gfortran.
** Newly obsolete macros
The following macros have been marked obsolete. New programs
should use the corresponding Gnulib modules. Gnulib not only
detects a larger set of portability problems with these functions,
but also provides complete workarounds.
AC_FUNC_ERROR_AT_LINE AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK
AC_FUNC_MKTIME AC_FUNC_STRTOD
* Major changes in Autoconf 2.67 (2010-07-21) [stable]
Released by Eric Blake, based on git versions 2.66.*.
** AC_CONFIG_SUBDIRS with more than one subdirectory at a time works again.
Regression introduced in 2.66.
** AC_CHECK_SIZEOF of a pointer type works again. Regression introduced in
2.66.
** New macro AC_FC_LINE_LENGTH to accept long Fortran source code lines.
** AC_PREPROC_IFELSE now keeps the preprocessed output in the conftest.i
file for inspection by the commands in the ACTION-IF-TRUE argument.
** AC_INIT again allows parentheses and other characters that are literal
in single- or double-quoted strings, and in quoted and unquoted
here-documents, for its PACKAGE and VERSION arguments. Regression
introduced in 2.66.
** autoreconf passes warning flags to new enough versions of aclocal.
** Running an Autotest testsuite in parallel mode no longer triggers a
race condition that could cause the testsuite run to end early,
fixing a sporadic failure in autoconf's own testsuite. Bug present
since introduction of parallel tests in 2.63b.
* Major changes in Autoconf 2.66 (2010-07-02) [stable]
Released by Eric Blake, based on git versions 2.65.*.
** AC_FUNC_MMAP works in C++ mode again. Regression introduced in 2.65.
** Use of m4_divert without a named diversion now issues a syntax warning,
since it is seldom right to change diversions behind autoconf's back.
** The macros AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, and
AC_TYPE_INT64_T work again. Regression introduced in 2.65.
** AC_PROG_INSTALL correctly uses 'shtool' again. Regression introduced
in 2.64.
** Autoconf should work on EBCDIC hosts.
** AC_CHECK_DECL and AC_CHECK_DECLS accept optional function argument types
for overloaded C++ functions.
** AS_SET_CATFILE accepts nonliterals in its variable name argument now.
** Autotest testsuites accept an option --recheck to rerun tests that
failed or passed unexpectedly during the last non-debug testsuite run.
** AC_ARG_ENABLE and AC_ARG_WITH now also accept '+' signs in '--enable-*'
and '--with-*' arguments, converting them to underscores for the variable
names.
** In configure scripts, loading CONFIG_SITE no longer searches PATH,
and problems in loading the configuration site files are diagnosed.
** Autotest testsuites may optionally provide colored test results.
** The previously undocumented Autotest macros AT_ARG_OPTION and
AT_ARG_OPTION_ARG have seen bug fixes and are documented now.
AT_ARG_OPTION has been changed in that the negative of a long option
--OPTION is now --no-OPTION rather than --noOPTION.
** The macro AS_LITERAL_IF is slightly more conservative; text
containing shell quotes are no longer treated as literals.
Furthermore, a new macro, AS_LITERAL_WORD_IF, adds an additional
level of checking that no whitespace occurs in literals.
** The macros AS_TR_SH and AS_TR_CPP no longer expand their results.
** The following macros are now documented:
AS_BOX
** New macro AC_FC_FIXEDFORM to accept fixed-form Fortran.
* Major changes in Autoconf 2.65 (2009-11-21) [stable]
Released by Eric Blake, based on git versions 2.64.*.
** Autoconf is now licensed under the General Public License version 3
or later (GPLv3+). As with earlier versions, the license includes
an exception clause so that you may release a configure script
generated by autoconf under the license of your own program.
** New macros to support Objective C++.
AC_PROG_OBJCXX AC_PROG_OBJCXXCPP
** The following undocumented autoconf macros, removed in Autoconf 2.64,
have been reinstated:
AH_CHECK_HEADERS
These macros are present only for backwards compatibility purposes.
** The macro AC_LANG_COMPILER no longer fails on embedded systems that
lack fopen in the C library, such as AVR or RTEMS (regression
introduced in 2.64).
** The AC_FC_FREEFORM macro no longer suffers from a whitespace bug that
made it fail with some Fortran compilers (regression introduced in
2.64).
** The AC_TYPE_UINT64_T and AC_TYPE_INT64_T macros have been fixed to no
longer mistakenly select a 32-bit type on some compilers (bug present
since macros were introduced in 2.59c).
** The AC_FUNC_MMAP macro has been fixed to be portable to systems like
Cygwin (bug present since macro was introduced in 2.0).
** The following documented autotest macros are new:
AT_CHECK_EUNIT
** The following m4sugar macros now quote their expansion:
m4_toupper m4_tolower
** The following m4sugar macros are new:
m4_escape
** The m4sugar macro m4_text_wrap now copes with embedded quoting without
requiring quadrigraphs. For uses like AC_ARG_VAR([a], [[b c]]),
this gives the intuitive behavior of "[b c]" in the output (2.63
gave the output of "[b], [c]", and 2.64 encountered a failure).
** The '$tmp' temporary directory used in config.status is documented for
public use now.
** config.status now provides a --config option to produce the configuration.
** Many cache variables used by Autoconf's macros are now documented.
** Configure scripts work better on DJGPP by avoiding a bug present in
the DJGPP port of bash 2.04 in handling 'return' in a shell
function (regression introduced in 2.64).
* Major changes in Autoconf 2.64 (2009-07-26) [stable]
Released by Eric Blake, based on git versions 2.63b.*.
** Autoconf now requires GNU M4 1.4.6 or later. Earlier versions of M4
have a bug in regular expression handling that interferes with some
of the speedups provided since Autoconf 2.63. GNU M4 1.4.13 or
later is recommended.
** AS_IF and AS_CASE have been taught to avoid syntax errors even when
given arguments that expand to just whitespace.
** The following documented autoconf macros are new:
AC_ERLANG_SUBST_ERTS_VER
** The autoheader tool now understands m4 macro arguments passed to
AC_DEFINE and AC_DEFINE_UNQUOTED.
** Ensure AT_CHECK can support commands that include a # given with
proper m4 quoting. For shell comments, this is a new feature; for
non-shell comments, this fixes a regression introduced in 2.63b.
Additionally, AT_CHECK correctly supplies shell escapes for
metacharacters occurring in m4 macro expansions within the expected
stdout and stderr parameters.
** The macro AT_CHECK now understands the concept of hard failure. If
a test exits with an unexpected status 99, cleanup actions for the
test are inhibited and the test is treated as a failure regardless
of AT_XFAIL_IF. It also understands the new directives
ignore-nolog, stdout-nolog, and stderr-nolog.
** The following documented autotest macros are new:
AT_CHECK_UNQUOTED AT_FAIL_IF AT_SKIP_IF
** The following documented m4sugar macros are new:
m4_argn m4_copy_force m4_default_nblank m4_default_nblank_quoted
m4_ifblank m4_ifnblank m4_rename_force
** The autoconf testsuite now exercises all Erlang macros.
* Major changes in Autoconf 2.63b (2009-03-31) [beta]
Released by Eric Blake, based on git versions 2.63.*.
** The manual is now shipped under the terms of the GNU FDL 1.3.