From: Richard Biener <rguenther@suse.de>
To: NightStrike <nightstrike@gmail.com>
Cc: Gaius Mulley <gaiusmod2@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] modula2/108144 - Fix multilib install of libgm2
Date: Mon, 23 Jan 2023 07:26:06 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2301230725170.6551@jbgna.fhfr.qr> (raw)
In-Reply-To: <CAF1jjLtaY0a16H7+VKbhBLoJQFAFD6FXyz1V9EHO57__5ar6yQ@mail.gmail.com>
On Fri, 20 Jan 2023, NightStrike wrote:
> On Fri, Jan 20, 2023 at 1:40 PM Gaius Mulley via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > Richard Biener <rguenther@suse.de> writes:
> >
> > > The following adjusts libgm2 to properly use the multilib build
> > > infrastructure, thereby fixing the install with
> > > --enable-version-specific-runtime-libs
> > >
> > > In particular config-ml.pl needs to be applied to generated Makefiles
> > > as documented in the manual and we have to avoid clobbering the
> > > variables via make arguments. The explicit install rules used different
> > > ways to construct the multilib dir which isn't necessary and breaks
> > > when MUTLIDIR is now finally set correctly. Instead use
> > > $(toolexeclibdir).
> > >
> > > This results in some dead variables in the Makefile.am (and there were
> > > some before), I refrained from doing even more changes here.
> > >
> > > Verified with an install with and without --enable-version-specific-runtime-libs
> > > and checking the result.
> > >
> > > OK?
> > >
> > > Thanks,
> > > Richard.
> >
> > Many thanks for this fix - and the deep magic AC_FOREACH config-ml.in
> > recursion rhunes. LGTM
> >
> > regards,
> > Gaius
>
> AC_FOREACH is obsolete and shouldn't be used in new code. It's been
> replaced with m4_foreach_w:
> https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Obsolete-Macros.html
I've pushed with AC_FOREACH which I cut&pasted from elsewhere. If
somebody feels like replacing all AC_FOREACH in the tree then that's
of course good.
Richard.
next prev parent reply other threads:[~2023-01-23 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63ca8324.170a0220.3a893.0660SMTPIN_ADDED_MISSING@mx.google.com>
2023-01-20 18:39 ` Gaius Mulley
2023-01-20 18:49 ` NightStrike
2023-01-23 7:26 ` Richard Biener [this message]
2023-01-20 12:03 Richard Biener
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=nycvar.YFH.7.77.849.2301230725170.6551@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.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).