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

Follow-up Comment #2, sr #110475 (project autoconf): I am sorry I reported this issue against Autoconf then. I am no expert in Autoconf/Automake, and I often find it difficult to pin-point where such problems are coming from. I found the following development site for Automake:

[sr #110476] ar: `u' modifier ignored since `D' is the default (see `U')

Follow-up Comment #2, sr #110476 (project autoconf): I am the original submitter of this bug report and I cannot find a way to close it either. Furthermore, I cannot change any status fields, it looks like I can only add comments. ___

Re: How to prevent warning "The macro `AC_PROG_CC_C99' is obsolete"

Actually, the trouble is that OpenOCD is not consistently using the m4_version_prereq solution. You're getting the message from the unprotected call to AC_PROG_CC_C99 in openocd-code/src/jtag/drivers/libjaylink/configure.ac. I hadn't realised, many thanks for your help. That file actually

How to prevent warning "The macro `AC_PROG_CC_C99' is obsolete"

Hi all: Macro AC_PROG_CC_C99 is obsolete as of Autoconf version 2.70 . Projects like OpenOCD are resorting to this kind of workaround: m4_version_prereq([2.70],[],[AC_PROG_CC_C99]) You can see it here: https://sourceforge.net/p/openocd/code/ci/master/tree/configure.ac Other projects are

Accelerate the 'configure' script

Hi all: I have this cross-compiling Autoconf project: https://github.com/rdiez/JtagDue/tree/master/Project I am not using Autoconf for portability, but mainly for handling C/C++ dependencies, so that not everything is rebuilt when I change one source file. This is just an example project, I

[sr #110476] ar: `u' modifier ignored since `D' is the default (see `U')

URL: Summary: ar: `u' modifier ignored since `D' is the default (see `U') Project: Autoconf Submitted by: rdiez Submitted on: Thu 22 Apr 2021 07:41:44 AM UTC Category: None

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

URL: Summary: ranlib: plugin needed to handle lto object Project: Autoconf Submitted by: rdiez Submitted on: Thu 22 Apr 2021 07:32:38 AM UTC Category: None

Re: How to change the shebang in 'configure' to require Bash

ars. But trying to change the shell requirement now is probably a big nightmare. Requiring a POSIX shell in the next version is an improvement, but POSIX is too limiting to really help. It is 2018. No wonder so many people want to ditch Autoconf! Best regards, R. D

How to change the shebang in 'configure' to require Bash

Hi all: I find it hard to write POSIX-compliant shell scripts. The lack of the 'pipefail' flag is specially problematic. I have described this issue here: http://rdiez.shoutwiki.com/wiki/Error_Handling_in_General_and_C%2B%2B_Exceptions_in_Particular#Set_the_pipefail_flag Therefore, I write