From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Michael Meissner <meissner@linux.vnet.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] New configuration options to enable additional executable/startfile/shared library prefixes
Date: Mon, 05 Nov 2012 17:27:00 -0000 [thread overview]
Message-ID: <20121105172727.GA30283@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <CAGWvnykQLp171sX=csmK56_8f5inA3GF_ybFODUTfdyX9mLuOw@mail.gmail.com>
On Sat, Nov 03, 2012 at 07:01:04PM -0400, David Edelsohn wrote:
> On Thu, Nov 1, 2012 at 5:17 PM, Michael Meissner
> <meissner@linux.vnet.ibm.com> wrote:
>
> > This patch adds 4 additional configuration switches, that allow the person
> > building the compiler to add additional prefixes to search for additional
> > executables and startfiles.
> >
> > If the backend has the appropriate tweaks installed, it will also add
> > additional prefixes to search for the dynamic linker. At the moment, only the
> > PowerPC Linux port has the modifications. It is fairly easy to modify other
> > targets if desired.
>
> Why does the documentation refer to powerpc64-linux when the changes
> affect all PowerPC Linux and affect the 32 bit dynamic linker search
> path?
Yes, obviously I should have included powerpc-linux as well as powerpc64-linux
in the documentation. Thanks. If it is approved, I will update the
documentation.
--
Michael Meissner, IBM
5 Technology Place Drive, M/S 2757, Westford, MA 01886-3141, USA
meissner@linux.vnet.ibm.com fax +1 (978) 399-6899
next prev parent reply other threads:[~2012-11-05 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 22:54 Michael Meissner
2012-11-01 23:22 ` Gerald Pfeifer
2012-11-02 18:01 ` Michael Meissner
2012-11-03 23:01 ` David Edelsohn
2012-11-05 17:27 ` Michael Meissner [this message]
2012-11-06 14:59 ` David Edelsohn
2012-12-05 19:47 ` Ping: " Michael Meissner
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=20121105172727.GA30283@ibm-tiger.the-meissners.org \
--to=meissner@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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).