[sr #111044] autoconf should assert existence of all subsidiary tools at startup

y real reports that e.g. diff was > missing on some real platforms, which led autoconf astray and ended up > in misconfigured build trees. Perhaps autoconf can afford to do some > sanity checking on these reasonable-sounding but not-universal > expectations. Zack Weinberg: > Frank

Re: [sr #111044] autoconf should assert existence of all subsidiary tools at startup

On Mon, Apr 1, 2024, at 5:26 PM, Frank Ch. Eigler wrote: > On Mon, Apr 01, 2024 at 05:10:17PM -0400, Paul Eggert wrote: >> [...] >> Not sure I'd go that far. The >> [https://www.gnu.org/prep/standards/html_node/Utilities-in-Makefiles.html GNU >> Coding Standards for utilities in makefiles] lists

[sr #111044] autoconf should assert existence of all subsidiary tools at startup

Update of sr #111044 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually Severity: 3 - Normal => 2 - Minor Status:None => Need Info

[sr #111016] Configure script fails to detect sctp on Alpine linux

Update of sr#111016 (group autoconf): Open/Closed:Open => Closed ___ Reply to this item at: ___

Re: [PATCH] Fix typo which causes test "m4_warn (bad categories)" to, fail.

On Thu, Feb 1, 2024, at 7:00 AM, Collin Funk wrote: > Hello, I ran into a test failure for "m4_warn (bad categories)". I > believe that this is just a typo introduced by commit b553b19. I > attached a patch that fixes the test failure. Your patch is correct, but incomplete. The typo was

Re: cannot make gcc report undeclared builtins

On Wed, Jan 31, 2024, at 6:23 AM, Simon Josefsson via Bug reports for autoconf wrote: > I got this failure on a loong64 machine for libidn2 that was > bootstrapped with autoconf 2.72: > > checking for gcc options needed to detect all undeclared functions... > cannot detect > configure: error: in

[sr #111007] autoconf 2.72 warning: file 'version.m4' included several times

Update of sr#111007 (group autoconf): Priority: 5 - Unprioritized => 8 - Release N (Blocker) ___ Follow-up Comment #3: Introducing an annoying, spurious warning on code recommended by the automake manual does seem

[sr #110989] Improve reliability of AT_MTIME_DELAY in test suite with a loop

Follow-up Comment #2, sr#110989 (group autoconf): No, if I understood Nick and Jacob's suggestions correctly, the idea is to replace $am_sleep / AT_MTIME_DELAY with something like while [ ! newer_file -nt older_file ]; do sleep $am_cv_filesystem_timestamp_resolution touch newer_file done

autoconf-2.72 released [stable]

Giaquinta (2) Eric Blake (4) Gleb Fotengauer-Malinovskiy (1) Jim Meyering (5) KO Myung-Hun (1) Keno Fischer (1) Marshall Ward (1) Mike Frysinger (1) Paul Eggert (84) Sergei Trofimovich (1) Todd C. Miller (1) Xi Ruoyao (1) Zack Weinberg (57) We would also like to thank everyone who

[sr #110987] AC_PROG_CC_C_O + AC_LANG([C++]) combines C-specific compiler options with C++ source

Update of sr#110987 (group autoconf): Status: Confirmed => Done Open/Closed:Open => Closed ___ Follow-up Comment #2: Turns out there is

[sr #110989] Improve reliability of AT_MTIME_DELAY in test suite with a loop

Update of sr#110989 (group autoconf): Priority: 5 - Unprioritized => 3 - Release N+1 ___ Reply to this item at: ___

[sr #110989] Improve reliability of AT_MTIME_DELAY in test suite with a loop

: None ___ Follow-up Comments: --- Date: Fri 22 Dec 2023 04:21:35 PM UTC By: Zack Weinberg Recording this idea for the next release cycle: On Fri, Dec 22, 2023, at 10:08 AM, Nick Bowler wrote: > On 2023-12-22 09

Re: [GNU Autoconf 2.72e] testsuite: 11 119 261 failed on Solaris 11.4 x86

On Fri, Dec 22, 2023, at 8:22 AM, Zack Weinberg wrote: > (But I'll also see if it's practical to mark this test as an expected > failure on systems where the write error isn't detected.) Thus. Tested only on Linux. I don't have access to a machine that has *both* /dev/full and a buggy pr

Re: [GNU Autoconf 2.72e] testsuite: 11 119 261 failed on Solaris 11.4 x86

On Thu, Dec 21, 2023, at 11:54 PM, Nick Bowler wrote: > On 2023-12-21 19:26, Paul Eggert wrote: >> On 2023-12-21 13:19, Zack Weinberg wrote: >>> Sorry, I'm with GNU here: failure to report errors on writing to >>> stdout is a bug. No excuses will be accepted. >

Re: [GNU Autoconf 2.72e] testsuite: 11 119 261 failed on Solaris 11.4 x86

On Thu, Dec 21, 2023, at 3:51 PM, Nick Bowler wrote: > On 2023-12-21 13:48, Zack Weinberg wrote: > > and an unsuccessful exit status. I would guess that on your machine > > the printf built-in and/or standalone printf executable are not > > reporting writ

[sr #110986] "autoconf: forbidden tokens, basic" testsuite failure on some systems

Follow-up Comment #2, sr#110986 (group autoconf): This is a regression caused by commit , "Fix timing bug on high-speed builds". That commit changed autom4te's logic for deciding whether its

Re: m4_foreach_w(...AC_DEFINE...) expansion change in 2.72e?

On Thu, Dec 21, 2023, at 2:39 PM, Paul Eggert wrote: > I'm seeing the same bug with Autoconf 2.69 on RHEL 7. Tarball attached > with the configure.ac that I used, and the output of "autoheader" and > "autoconf". Thanks for checking, Paul. I see the same phenomenon with 2.71, I can't reproduce

Re: m4_foreach_w(...AC_DEFINE...) expansion change in 2.72e?

On Thu, Dec 21, 2023, at 2:20 PM, Zack Weinberg wrote: > On Thu, Dec 21, 2023, at 1:40 PM, Karl Berry wrote: >> 2.72e creates a different autoconf.h.in and configure in TeX Live's >> texk/lcdf-typetools >> (https://github.com/TeX-Live/texlive-source/tree/trun

Re: m4_foreach_w(...AC_DEFINE...) expansion change in 2.72e?

On Thu, Dec 21, 2023, at 1:40 PM, Karl Berry wrote: > 2.72e creates a different autoconf.h.in and configure in TeX Live's > texk/lcdf-typetools > (https://github.com/TeX-Live/texlive-source/tree/trunk/texk/lcdf-typetools): ... > In other words, what was four separate HAVE_AUTO_* macros have become

Re: [GNU Autoconf 2.72e] testsuite: 11 332 failed on OS X 10.9

On Thu, Dec 21, 2023, at 1:32 PM, Sevan Janiyan wrote: > Intel laptop running 10.10.5, m4 included with OS is too old > (1.4.6), so GNU m4 1.4.18 was used. ... > ERROR: 549 tests were run, > 6 failed (4 expected failures). > 60 tests were skipped. (ignoring test #11, as that's a known issue) ...

[sr #110987] AC_PROG_CC_C_O + AC_LANG([C++]) combines C-specific compiler options with C++ source

Update of sr#110987 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually ___ Follow-up Comment #1: Low priority as this affects only unusual configure.ac layout, and as all of the AC_PROG_*_C_O

[sr #110987] AC_PROG_CC_C_O + AC_LANG([C++]) combines C-specific compiler options with C++ source

: None ___ Follow-up Comments: --- Date: Thu 21 Dec 2023 07:14:49 PM UTC By: Zack Weinberg A configure.ac like this AC_INIT AC_LANG([C++]) AC_PROG_CC_C_O ... may (depending on exactly which co

Re: [GNU Autoconf 2.72e] testsuite: 11 119 261 failed on Solaris 11.4 x86

On Thu, Dec 21, 2023, at 12:34 PM, Alan Coopersmith wrote: > For 119, the code in the Solaris find command that prints the > "find: cannot read dir sub/unwritable" message was modified last year > to make it not print that message if -prune was in effect for the directory, > so it's possible a bug

Re: [GNU Autoconf 2.72e] testsuite: 11 40 41 45 280 281 282 286 287 failed on OS X 10.4

On Thu, Dec 21, 2023, at 9:03 AM, Zack Weinberg wrote: > On Wed, Dec 20, 2023, at 6:29 PM, Sevan Janiyan wrote: >> aclocal: unrecognized option -- `--system-acdir=/Users/sme/tmp/autoconf- >> 2.72e/tests/testsuite.dir/040/empty' > > This means your automake, version 1.6.3, is

Re: [GNU Autoconf 2.72e] testsuite: 11 119 261 failed on Solaris 11.4 x86

On Wed, Dec 20, 2023, at 4:57 PM, Alan Coopersmith wrote: > Failed tests: > GNU Autoconf 2.72e test suite test groups: > > NUM: FILE-NAME:LINE TEST-GROUP-NAME >KEYWORDS > >11: tools.at:442 autoconf: forbidden tokens, basic > 119: m4sh.at:2115 _AS_CLEAN_DIR > 261:

Re: [GNU Autoconf 2.72e] testsuite: 11 40 41 45 280 281 282 286 287 failed on OS X 10.4

On Wed, Dec 20, 2023, at 6:29 PM, Sevan Janiyan wrote: > G5 running OS X 10.4.11, m4 included with OS is too old (1.4.2), so GNU > m4 1.4.19 was used. Thanks for all the testing. The failure of test #11 is a known, minor issue, see . >40:

autoconf-2.72e released [release candidate]

contributed! The following people contributed changes to this release: Bruno Haible (1) Detlef Riekenberg (1) Paul Eggert (5) Zack Weinberg (12) zw [on behalf of the autoconf maintainers] == Here is the GNU autoconf home

[sr #110986] "autoconf: forbidden tokens, basic" testsuite failure on some systems

Update of sr#110986 (group autoconf): Priority: 5 - Unprioritized => 3 - Release N+1 ___ Follow-up Comment #1: The worst practical consequence of this is only that we may run M4 more often than we needed to,

[sr #110986] "autoconf: forbidden tokens, basic" testsuite failure on some systems

ing System: None ___ Follow-up Comments: --- Date: Wed 20 Dec 2023 02:11:14 PM UTC By: Zack Weinberg Observed by me on at least x86_64-netbsd9 and sparc64-solaris10: the "autoconf: forbidden tokens, basi

[sr #110985] "Substitute and define special characters" test fails on NetBSD 9

Update of sr#110985 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually ___ Reply to this item at: ___

[sr #110985] "Substitute and define special characters" test fails on NetBSD 9

ing System: None ___ Follow-up Comments: --- Date: Wed 20 Dec 2023 01:59:11 PM UTC By: Zack Weinberg On x86_64-unknown-netbsd9.3, running Autoconf's test suite consistently produces this failure: Failed tests: NUM

[sr #110983] AC_SYS_LARGEFILE doesn't honor AC_LANG setting

Follow-up Comment #4, sr#110983 (group autoconf): @Paul Eggert: Not today, hopefully tomorrow. ___ Reply to this item at: ___ Message sent via

[sr #110983] AC_SYS_LARGEFILE doesn't honor AC_LANG setting

Follow-up Comment #3, sr#110983 (group autoconf): As a workaround, make sure to invoke AC_SYS_LARGEFILE and/or AC_SYS_YEAR2038 early in configure.ac (this is a good idea anyway, as they can affect the results of later checks), in C mode, even if nothing else uses the C compiler. For example:

[sr #110983] AC_SYS_LARGEFILE doesn't honor AC_LANG setting

Update of sr#110983 (group autoconf): Priority: 5 - Unprioritized => 3 - Release N+1 Severity: 3 - Normal => 4 - Important Operating System: Solaris => None

[sr #110983] AC_SYS_LARGEFILE doesn't honor AC_LANG setting

olaris ___ Follow-up Comments: --- Date: Tue 19 Dec 2023 06:36:10 PM UTC By: Zack Weinberg _AC_SYS_LARGEFILE_PROBE unconditionally modifies $CC, regardless of the current AC_LANG setting. Therefore, a configure script like this A

[sr #110982] Autotest: add some way to declare an expected failure halfway through the test

Update of sr#110982 (group autoconf): Priority: 5 - Unprioritized => 3 - Release N+1 ___ Reply to this item at: ___

[sr #110982] Autotest: add some way to declare an expected failure halfway through the test

: None ___ Follow-up Comments: --- Date: Tue 19 Dec 2023 06:26:52 PM UTC By: Zack Weinberg Shell code in the argument of AT_XFAIL_IF is always executed at the very beginning of the test group, and, i

[sr #110503] Autoconf 2.70 problem: gkt-doc/gtkdocize is now unconditionally required

Update of sr#110503 (group autoconf): Priority: 7 - Release N (Desirable) => 3 - Release N+1 Status: Need Info => Confirmed ___ Follow-up Comment #7: I understand the

[sr #110554] AC_CONFIG_HEADERS doesn't work properly for files with Windows line-endings

Update of sr#110554 (group autoconf): Priority: 7 - Release N (Desirable) => 3 - Release N+1 Status: Ready For Test => In Progress ___ Follow-up Comment #2: Turns out either

[sr #110927] 30 tests fail building on macOS Venture 13.5.1 with Xcode 14.3.1

Update of sr#110927 (group autoconf): Status: Ready For Test => Done Open/Closed:Open => Closed ___ Reply to this item at:

[sr #110872] m4_warn differs in various ways from its documentation

Update of sr#110872 (group autoconf): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #2: Revised, committed

[sr #110872] m4_warn differs in various ways from its documentation

Update of sr#110872 (group autoconf): Status: Confirmed => In Progress ___ Follow-up Comment #1: Candidate patch: .

[sr #110554] AC_CONFIG_HEADERS doesn't work properly for files with Windows line-endings

Update of sr#110554 (group autoconf): Status: Confirmed => Ready For Test ___ Follow-up Comment #1: Should be fixed in

[sr #110746] GNU Autoconf 2.71: F77 name-mangling fails when compiling with mpicxx

Update of sr#110746 (group autoconf): Status: Need Info => Done Open/Closed:Open => Closed ___ Follow-up Comment #3: I'm going to go

[sr #110971] busybox mkdir is misdetected

Update of sr#110971 (group autoconf): Status: Confirmed => Done Open/Closed:Open => Closed ___ Follow-up Comment #7: Paul's patch

[sr #110713] Use __STDC__VERSION as first test for C99 compatibility (patch attached)

Update of sr#110713 (group autoconf): Status: Confirmed => Done Open/Closed:Open => Closed ___ Follow-up Comment #4: Committed now with a

[sr #110561] autoconf: store autom4te request keys in sorted order

Update of sr#110561 (group autoconf): Status: Confirmed => Done Open/Closed:Open => Closed ___ Follow-up Comment #2: Your patch was

[sr #110318] autoreconf: support libtoolize being named glibtoolize

Update of sr#110318 (group autoconf): Priority: 7 - Release N (Desirable) => 3 - Release N+1 ___ Follow-up Comment #6: I looked into this a bit more, and it turns out I was wrong, it's not easy. autoreconf doesn't

[sr #110927] 30 tests fail building on macOS Venture 13.5.1 with Xcode 14.3.1

Follow-up Comment #2, sr#110927 (group autoconf): I tested current development trunk on macOS 12 with Xcode 14.2 (and GNU M4 1.4.19 from Homebrew; on macOS, Autoconf no longer supports use of the system-provided M4 1.4.6) and observed no failures. If I do not hear from you, or someone else, to

Bug triage for 2.72 complete; release freeze begins now

Bug triage for 2.72 is complete. All bug-autoconf subscribers, thank you for your patience with the flood of low-information email. I intend to make the final release of 2.72 no sooner than Monday, Dec. 18, but no *later* than Friday, Dec. 22. Please consider the 'master' branch to be in

[sr #110416] documentation: ordering of basic macros?

Update of sr#110416 (group autoconf): Priority: 2 - Eventually => 3 - Release N+1 ___ Reply to this item at: ___

[sr #110886] autoupdate produces broken configure.ac

Update of sr#110886 (group autoconf): Priority: 2 - Eventually => 1 - Blocked ___ Reply to this item at: ___

[sr #110537] AC_SEARCH_LIBS does not honor --with-sysroot=

Update of sr#110537 (group autoconf): Priority: 2 - Eventually => 1 - Blocked ___ Reply to this item at: ___

[sr #110382] Make confdefs.h idempotent vs compiler warnings

Update of sr#110382 (group autoconf): Summary: Make confdefs.h idempotent => Make confdefs.h idempotent vs compiler warnings ___ Reply to this item at:

[sr #110382] Make confdefs.h idempotent

Update of sr#110382 (group autoconf): Summary: In autoconf-2.69d AC_LANG_SOURCE implicitly includes '#include "confdefs.h"' => Make confdefs.h idempotent ___ Reply to this item at:

[sr #110435] autoreconf: recognize when AM_ICONV is used without the rest of gettext

Update of sr#110435 (group autoconf): Priority: 7 - Release N (Desirable) => 3 - Release N+1 Summary: autoreconf does not recognize AM_ICONV => autoreconf: recognize when AM_ICONV is used without the rest of gettext

[sr #110971] busybox mkdir is misdetected

Update of sr#110971 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110886] autoupdate produces broken configure.ac

Update of sr#110886 (group autoconf): Status:None => Postponed ___ Reply to this item at: ___

[sr #110713] Use __STDC__VERSION as first test for C99 compatibility (patch attached)

Update of sr#110713 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110872] m4_warn differs in various ways from its documentation

Update of sr#110872 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110612] Re-exec of $as_myself chooses wrong configure script from PATH

Update of sr#110612 (group autoconf): Status:None => Need Info ___ Follow-up Comment #4: This is all helpful but I'm leaving this marked "need info" until someone has the time to do a

[sr #110561] autoconf: store autom4te request keys in sorted order

Update of sr#110561 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110554] AC_CONFIG_HEADERS doesn't work properly for files with Windows line-endings

Update of sr#110554 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110537] AC_SEARCH_LIBS does not honor --with-sysroot=

Update of sr#110537 (group autoconf): Status:None => Need Info ___ Reply to this item at: ___

[sr #110435] autoreconf does not recognize AM_ICONV

Update of sr#110435 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110418] Unable to specify build and target perl in cross builds

Update of sr#110418 (group autoconf): Priority: 7 - Release N (Desirable) => 1 - Blocked Status:None => Need Info ___ Reply to this item at:

[sr #110395] Makefile generated from Makefile.in unqoute *FLAGS variable twice while ./configure script only once

Update of sr#110395 (group autoconf): Status:None => Need Info ___ Reply to this item at: ___

[sr #110394] Support optional use of the C++ compiler in AC_PROG_CXX (and similarly for other languages)

Update of sr#110394 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110354] Parallel autotest produces mangled output on Solaris 10

Update of sr#110354 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110348] Simplify rules for when configure enters cross-compiling mode

Update of sr#110348 (group autoconf): Status:None => Need Info ___ Reply to this item at: ___

[sr #110308] Upstream: yocto/autoreconf-exclude.patch

Update of sr#110308 (group autoconf): Status:None => Need Info ___ Reply to this item at: ___

[sr #110347] Revise documentation of when configure enters cross-compilation mode.

Update of sr#110347 (group autoconf): Status:None => Confirmed ___ Reply to this item at: ___

[sr #110307] Upstream: netbsd/patch-lib_autoconf_fortran.m4

Update of sr#110307 (group autoconf): Status:None => Need Info ___ Reply to this item at: ___

[sr #110852] autoconf 2.71 checking command to parse /usr/bin/nm -B output from gcc object

Update of sr#110852 (group autoconf): Priority: 5 - Unprioritized => 1 - Blocked Status:None => Need Info ___ Follow-up Comment #2: I regret the delay

[sr #110713] Use __STDC__VERSION as first test for C99 compatibility (patch attached)

Update of sr#110713 (group autoconf): Priority: 5 - Unprioritized => 7 - Release N (Desirable) ___ Reply to this item at: ___

[sr #110561] autoconf: store autom4te request keys in sorted order

Update of sr#110561 (group autoconf): Priority: 5 - Unprioritized => 7 - Release N (Desirable) ___ Follow-up Comment #1: We will need to tweak the patch so that it falls back to the old behavior when we have an old

[sr #110554] AC_CONFIG_HEADERS doesn't work properly for files with Windows line-endings

Update of sr#110554 (group autoconf): Priority: 5 - Unprioritized => 7 - Release N (Desirable) ___ Reply to this item at: ___

[sr #110503] Autoconf 2.70 problem: gkt-doc/gtkdocize is now unconditionally required

Update of sr#110503 (group autoconf): Priority: 5 - Unprioritized => 7 - Release N (Desirable) ___ Reply to this item at: ___

[sr #110872] m4_warn differs in various ways from its documentation

Update of sr#110872 (group autoconf): Priority: 5 - Unprioritized => 7 - Release N (Desirable) ___ Reply to this item at: ___

[sr #110497] "This script requires a shell more modern than all the shells I found" message should suggest something

Update of sr#110497 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually Status: Confirmed => Need Info ___ Follow-up Comment #1: Before we can start

[sr #110537] AC_SEARCH_LIBS does not honor --with-sysroot=

Update of sr#110537 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually ___ Reply to this item at: ___

[sr #110886] autoupdate produces broken configure.ac

Update of sr#110886 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually ___ Follow-up Comment #7: To reiterate, all the issues described in this bug report are caused by limitations in autoupdate

[sr #110746] GNU Autoconf 2.71: F77 name-mangling fails when compiling with mpicxx

Update of sr#110746 (group autoconf): Priority: 5 - Unprioritized => 1 - Blocked ___ Reply to this item at: ___

[sr #110573] AR_CONFIG_AUX_DIR(S) does not recognize shell vars nor absolute paths

Update of sr#110573 (group autoconf): Priority: 5 - Unprioritized => 1 - Blocked ___ Reply to this item at: ___

[sr #110846] cross-compilation is not entered when build_alias and host_alias are the same

Follow-up Comment #2, sr#110846 (group autoconf): Note that cross compilation mode _can_ be forced on, today, with e.g. ./configure --host=aarch64-unknown-linux-gnu cross_compiling=yes ___ Reply to this item at:

[sr #110348] Simplify rules for when configure enters cross-compiling mode

Follow-up Comment #2, sr#110348 (group autoconf): Nick Bowler raised a serious concern about this change in email: > You can already force cross-compilation mode today by running > > ./configure cross_compiling=yes > > I think it would be better to simply document this more clearly. >

[sr #110318] autoreconf: support libtoolize being named glibtoolize

Update of sr#110318 (group autoconf): Priority: 3 - Release N+1 => 7 - Release N (Desirable) ___ Follow-up Comment #5: Actually this should be easy. ___

[sr #110435] autoreconf does not recognize AM_ICONV

Update of sr#110435 (group autoconf): Priority: 2 - Eventually => 7 - Release N (Desirable) ___ Follow-up Comment #5: Hmm, if it's that simple I'll put it back on the "if we have time" list for 2.72.

[sr #110879] revert forcing/setting -std=gnu++11 by default (introduced in Autoconf 2.70)

Follow-up Comment #4, sr#110879 (group autoconf): The troublesome behavior has been present for three years now and many projects have come to depend on it, thus a straight revert is not possible anymore. However, #110286 is now being treated as a bug, not just a new feature request.

[sr #110492] Some tests failed on Mac OS X Catalina, please see the logfile.

Update of sr#110492 (group autoconf): Status:None => Not Autoconf Open/Closed:Open => Closed ___ Follow-up Comment #2: Concurring with

[sr #110484] CFLAGS/CXXFLAGS and CPPFLAGS order in c.m4 ac_compile is nonstandard

Update of sr#110484 (group autoconf): Open/Closed:Open => Closed ___ Reply to this item at: ___

[sr #110484] CFLAGS/CXXFLAGS and CPPFLAGS order in c.m4 ac_compile is nonstandard

Update of sr#110484 (group autoconf): Severity: 4 - Important => 3 - Normal Status:None => Invalid ___ Follow-up Comment #1: Autoconf is

[sr #110480] Generated configure script has errors

Update of sr#110480 (group autoconf): Priority: 5 - Unprioritized => 1 - Blocked Status:None => Need Info ___ Follow-up Comment #3: We can't do anything

[sr #110478] support for slibtool ans optional replacement for GNU libtool

Update of sr#110478 (group autoconf): Priority: 5 - Unprioritized => 1 - Blocked Status:None => Need Changes Elsewhere ___ Follow-up Comment #1: I'm delighted to

[sr #110475] ranlib: plugin needed to handle lto object

Update of sr#110475 (group autoconf): Open/Closed:Open => Closed ___ Follow-up Comment #4: Closing. R. Diez, please understand that it really does need to be _you_ who files the bug

[sr #110473] Building project fails when space or parenthesis is in the path

Update of sr#110473 (group autoconf): Status:None => Not Autoconf Open/Closed:Open => Closed ___ Follow-up Comment #1: This needs to be

[sr #110879] revert forcing/setting -std=gnu++11 by default (introduced in Autoconf 2.70)

Update of sr#110879 (group autoconf): Open/Closed:Open => Closed ___ Reply to this item at: ___

[sr #110286] Make it possible to request a specific (non-latest) version of a language standard

Update of sr#110286 (group autoconf): Severity:1 - Wish => 4 - Important Status:None => Confirmed ___ Follow-up Comment #2: Because we have

[sr #110879] revert forcing/setting -std=gnu++11 by default (introduced in Autoconf 2.70)

Update of sr#110879 (group autoconf): Status:None => Duplicate ___ Follow-up Comment #2: Effectively a duplicate of bug #110286 which I will treat as a priority item for 2.73. No

[sr #110451] autoconf 2.71 generated configure file does not enable C compiler flag for C99 on Solaris 10

Update of sr#110451 (group autoconf): Priority: 5 - Unprioritized => 2 - Eventually Status: Need Info => Confirmed ___ Follow-up Comment #6: Someone who actually

  1   2   3   4   >