From: Andreas Schwab <schwab@linux-m68k.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] bfd: Properly install library and header files
Date: Sun, 23 Jan 2022 19:03:25 +0100 [thread overview]
Message-ID: <877daqxrbm.fsf@igel.home> (raw)
In-Reply-To: <Ye2TpWFUL3RWqcdF@vapier> (Mike Frysinger via Binutils's message of "Sun, 23 Jan 2022 12:43:01 -0500")
On Jan 23 2022, Mike Frysinger via Binutils wrote:
> your patch below does two things: renames the vars and deletes an install
> target. pretty sure only the latter is necessary to fix things. although
> i don't know the history behind why bfd uses these names.
That is needed for cross configurations, where bfd isn't installed in
the standard location. Renaming the variables will break that (see
AM_INSTALL_LIBBFD).
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-01-23 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 15:36 H.J. Lu
2022-01-23 17:43 ` Mike Frysinger
2022-01-23 18:03 ` Andreas Schwab [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=877daqxrbm.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=hjl.tools@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).