public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: "François-Xavier Coudert" <fxcoudert@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-5754] Build: fix error in fixinclude configure
Date: Wed, 22 Nov 2023 10:55:13 +0000 (GMT)	[thread overview]
Message-ID: <20231122105513.4BADF3858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:ce966ae66067d8d365431ef7a323f4207fcb729a

commit r14-5754-gce966ae66067d8d365431ef7a323f4207fcb729a
Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date:   Fri Nov 17 12:50:42 2023 +0100

    Build: fix error in fixinclude configure
    
    The stray line defining enable_darwin_at_rpath outside of the scope of
    _LT_DARWIN_LINKER_FEATURES is a mistake and should be removed. It leads
    to a wrong line in fixincludes/ChangeLog because there is no $1 argument
    at that point.
    
    ChangeLog:
    
            * libtool.m4: Fix stray call
    
    fixincludes/ChangeLog:
    
            * configure: Regenerated.

Diff:
---
 fixincludes/configure | 1 -
 libtool.m4            | 1 -
 2 files changed, 2 deletions(-)

diff --git a/fixincludes/configure b/fixincludes/configure
index 1bb547a1724..662c94dc112 100755
--- a/fixincludes/configure
+++ b/fixincludes/configure
@@ -3027,7 +3027,6 @@ ac_configure="$SHELL $ac_aux_dir/configure"  # Please don't use this var.
 # ---------------------------
 # _LT_COMPILER_PIC
 
-enable_darwin_at_rpath_$1=no
 
 # _LT_LINKER_SHLIBS([TAGNAME])
 # ----------------------------
diff --git a/libtool.m4 b/libtool.m4
index 7f8ae26db62..add2d4a1e23 100644
--- a/libtool.m4
+++ b/libtool.m4
@@ -4312,7 +4312,6 @@ _LT_TAGDECL([link_static_flag], [lt_prog_compiler_static], [1],
 	[Compiler flag to prevent dynamic linking])
 ])# _LT_COMPILER_PIC
 
-_LT_TAGVAR(enable_darwin_at_rpath, $1)=no
 
 # _LT_LINKER_SHLIBS([TAGNAME])
 # ----------------------------

                 reply	other threads:[~2023-11-22 10:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231122105513.4BADF3858D35@sourceware.org \
    --to=fxcoudert@gcc.gnu.org \
    --cc=gcc-cvs@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).