Setting ACLOCAL_AMFLAGS with ':=' vs '='

Hallo there: If I add this line to my Makefile.am (and I make sure that the 'm4' subdir is created beforehand), then it works as intended: ACLOCAL_AMFLAGS = -I m4 However, if I use this syntax: ACLOCAL_AMFLAGS := -I m4 Then I get the following warning: libtoolize: Consider adding `-I m

subdir-objects generates subdirs with unsubstituted variable names

Hi there: I have the following open-source project that cross-compiles to an embedded target: https://github.com/rdiez/JtagDue I am trying to keep automake happy in order to prevent the following kind of warnings: EmptyFirmware/Makefile.am:41: warning: source file '$(CMSIS_SRC_TEMPLATE_DI

Recompiling all sources when the makefile changes

Hi there: I have the following open-source project that cross-compiles to an embedded target: https://github.com/rdiez/JtagDue I am using Ubuntu 14.04, which comes with autoconf 2.69 and automake 1.14.1. I am building out of the source tree. I noticed that, if I change the version number in t

Re: Recompiling all sources when the makefile changes

First of all, thanks for your e-mail. > If "configure" is changing something, an easy and reliable option is > to > ensure that it changes config.h (or some other configuration header), > which will naturally cause a rebuild of files that include the header. This is not as straightforward as i

Re: Recompiling all sources when the makefile changes

> While it's your project and you can do this if you want, making > all objects depend on the makefile sounds like a really silly idea. > Nobody wants to spend 30 minutes recompiling because they added one > source file to a library, or because they added an additional test > case. > > I sugge

Please, please fix the subdir-objects out-of-tree bug

Hi Automake devs: I need to build some files outside of the build repository, and I cannot use option 'subdir-objects' because of an Automake bug, so I constantly get many warnings like this with newer Automake versions: warning: source file '$(BLAH_BLAH_DIR)/src/blah_blah.cpp' is in a sub

Prepending '+' to the recipe line when linking with GCC's -flto=jobserver

Hi all: I am developing firmware similar to this one: https://github.com/rdiez/JtagDue First, I am building a GCC 8.3.0 cross-compiler toolchain for ARM Cortex-M4F on Ubuntu 18.04.4 LTS, and I am then using it to build some embedded software with a cross-compiling Autoconf project. GCC intro

Re: Prepending '+' to the recipe line when linking with GCC's -flto=jobserver

[...] At any rate, it would be extremely helpful to have a minimal-as-possible runnable (automake-able) example showing the case where the + needs to be prepended. rdiez, can you create such a mini-project? > [...] I normally use Autoconf, and I do not understand very much the separation between

How to speed up 'automake'

Hi all: I have this cross-compiling Autoconf/Automake project: https://github.com/rdiez/JtagDue/tree/master/Project This is just an example project, I have others that are bigger, and I rebuild many of them automatically overnight. That is why I am looking at speeding up the Autotools steps.

"make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c"

Hi all: I have hit an interesting bug in Automake. It has taken me a few hours of learning and experimentation to track it down. The OpenOCD project uses the Autotools and everything seems fine: bootstrap, ./configure, "make install", etc. work fine. Only make "make dist" fails: $ make dist m

Re: "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c"

> [...] > Looking again at your message from last November (sorry) >https://lists.gnu.org/archive/html/automake/2024-11/msg0.html > I am puzzled as to what's going on. > Maybe you can provide a runnable example of the problem? First of all, thanks for your interest in getting to the bottom