public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Iain Sandoe <iains.gcc@gmail.com>,
	gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>
Subject: Re: Darwin: Replace environment runpath with embedded [PR88590]
Date: Wed, 15 Nov 2023 21:34:08 +0100	[thread overview]
Message-ID: <22AC949A-3CE2-47E0-83F6-9D0CC6B52C99@gmail.com> (raw)
In-Reply-To: <8734x6vktd.fsf@euler.schwinge.homeip.net>

> So I currently see the following in my build logs:
> 
>    [...]
>    mkdir -p -- ./fixincludes
>    Configuring in ./fixincludes
>    configure: creating cache ./config.cache
>    [...]/source-gcc/fixincludes/configure: line 3030: enable_darwin_at_rpath_--srcdir=[...]/source-gcc/fixincludes=no: No such file or directory
>    checking build system type... x86_64-pc-linux-gnu
>    checking host system type... x86_64-pc-linux-gnu
>    checking target system type... nvptx-unknown-none
>    [...]
> 
> I'm not convinced that's achieving what it means to achieve?

I’ve tried to understand where that line gets expanded from:

>>> +enable_darwin_at_rpath_$1=no

It comes from:

> _LT_TAGVAR(enable_darwin_at_rpath, $1)=no

in the top-level libtool.m4. I can’t say that I understand why that line is there. All the other definitions using this structure are all inside the definition of _LT_ prefixed functions, defined by m4_defun. This one line is alone, outside of any function.

If I remove the line from libtool.m4 (innocent smile) I see that fixincludes/configure is better, and it does not appear to change the regenerated files in other directories (I didn’t do a build yet, just tried to regenerate with some manual autoconf invocations).

Food for thought.
FX

  reply	other threads:[~2023-11-15 20:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 16:58 FX Coudert
2023-08-18 20:17 ` Joseph Myers
2023-08-18 22:31   ` Iain Sandoe
2023-08-18 22:59     ` Joseph Myers
2023-08-18 23:05       ` Iain Sandoe
2023-08-25  7:50   ` FX Coudert
2023-08-25 16:28     ` Joseph Myers
2023-08-29 16:06       ` FX Coudert
2023-08-29 19:55         ` Joseph Myers
2023-08-29 20:17           ` FX Coudert
2023-09-12 17:52             ` FX Coudert
2023-09-20 13:52               ` FX Coudert
2023-10-08 13:07                 ` Nathanael Nerode
2023-10-08 22:14                   ` Iain Sandoe
2023-10-21 18:05                     ` Jeff Law
2023-10-21 18:26                       ` Iain Sandoe
2023-10-21  5:27             ` Alexandre Oliva
2023-10-22 21:18               ` FX Coudert
2023-11-30 19:43                 ` Ian Lance Taylor
2023-11-30 19:56                   ` Iain Sandoe
2023-11-30 19:58                     ` Ian Lance Taylor
2023-11-30 21:25                       ` Ian Lance Taylor
2023-10-30 16:17 ` Martin Jambor
     [not found] ` <653fd72a.050a0220.a6a20.de86SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-30 16:19   ` Iain Sandoe
2023-10-30 16:31   ` FX Coudert
2023-10-30 19:08     ` Iain Sandoe
2023-11-15 20:11       ` Thomas Schwinge
2023-11-15 20:34         ` FX Coudert [this message]
2023-11-17 11:56           ` FX Coudert
2023-11-17 12:13             ` Thomas Schwinge
2023-11-17 14:20               ` FX Coudert
2023-11-22 10:52                 ` Iain Sandoe
2023-11-22 10:55                   ` FX Coudert
2023-11-13 15:27 ` gfortran.dg/dg.exp debug messages pollute test output Rainer Orth
2023-11-13 16:19   ` Iain Sandoe
2023-11-15 10:29     ` FX Coudert
2023-11-15 12:04       ` Rainer Orth
2023-11-17 12:36       ` Thomas Schwinge
2023-11-18  9:03         ` FX Coudert

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=22AC949A-3CE2-47E0-83F6-9D0CC6B52C99@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    --cc=mjambor@suse.cz \
    --cc=thomas@codesourcery.com \
    /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).