From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: hardcode AC_CONFIG_AUX_DIR path
Date: Mon, 10 Jan 2022 19:44:30 -0500 [thread overview]
Message-ID: <YdzS7sQBks7lVy47@vapier> (raw)
In-Reply-To: <Ydv6Ap+q5mHodXCC@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
On 10 Jan 2022 10:18, Corinna Vinschen wrote:
> On Jan 7 22:08, Mike Frysinger wrote:
> > In order to transition to automake, we have to use hardcoded paths in
> > the AC_CONFIG_AUX_DIR macro call (since automake evaluates the path
> > itself, and doesn't expand vars), so simplify all the calls here.
>
> Apparently we're not using multi.m4, so this should be safe.
i hadn't noticed that file before. another good reason to change newlib
and libgloss to use -I../config with aclocal :).
> I'm quite fuzzy in terms of this stuff, but I can't see a problem
> right now. Please push.
i've been testing bfin-elf which builds like 4 multilibs normally.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-01-11 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 3:08 Mike Frysinger
2022-01-10 9:18 ` Corinna Vinschen
2022-01-11 0:44 ` Mike Frysinger [this message]
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=YdzS7sQBks7lVy47@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.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).