public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: gcc-patches@gcc.gnu.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH] fixincludes: add AC_CONFIG_MACRO_DIRS to configure.ac
Date: Mon, 29 Apr 2024 22:24:18 -0400	[thread overview]
Message-ID: <20240430022420.114397-1-simon.marchi@polymtl.ca> (raw)

Add an "AC_CONFIG_MACRO_DIRS" call in configure.ac, with the same
directories as specified in "ACLOCAL_AMFLAGS", in Makefile.in.

This makes it possible to re-generate aclocal.m4 using "autoreconf".
---
 fixincludes/configure    | 1 +
 fixincludes/configure.ac | 1 +
 2 files changed, 2 insertions(+)

diff --git a/fixincludes/configure b/fixincludes/configure
index 662c94dc1120..7147c9a618aa 100755
--- a/fixincludes/configure
+++ b/fixincludes/configure
@@ -4627,6 +4627,7 @@ $as_echo "$ac_cv_path_SED" >&6; }
   rm -f conftest.sed
 
 
+
 # Figure out what compiler warnings we can enable.
 # See config/warnings.m4 for details.
 
diff --git a/fixincludes/configure.ac b/fixincludes/configure.ac
index 4e78511d20fc..3d177699ebfa 100644
--- a/fixincludes/configure.ac
+++ b/fixincludes/configure.ac
@@ -7,6 +7,7 @@ AC_CANONICAL_SYSTEM
 AC_PROG_CC
 AC_USE_SYSTEM_EXTENSIONS
 AC_PROG_SED
+AC_CONFIG_MACRO_DIRS([.. ../config])
 
 # Figure out what compiler warnings we can enable.
 # See config/warnings.m4 for details.

base-commit: 22b20ac6c6aead2d3f36c413a77dd0b80adfec39
-- 
2.44.0


             reply	other threads:[~2024-04-30  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  2:24 Simon Marchi [this message]
2024-04-30  8:54 ` Christophe Lyon
2024-04-30 15:47   ` Simon Marchi
2024-05-02 13:36     ` Christophe Lyon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240430022420.114397-1-simon.marchi@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).