public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Andi Kleen <andi@firstfloor.org>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC PATCH] update to libtool-2.4.2 and regenerate
Date: Sat, 29 Oct 2011 13:01:00 -0000	[thread overview]
Message-ID: <20111029090345.GB14103@one.firstfloor.org> (raw)
In-Reply-To: <20111029073937.GA1645@x4.trippels.de>

> I haven't figured out yet how to use gcc-ar et al. instead of the shell
> wrappers. The plugin path seems to be hardcoded, which is unfortunate.
> Would it be possible to make the wrappers more flexible, so that they
> could be used during bootstrap?

The path can be set with GCC_EXEC_PREFIX currently. Maybe the makefile
could set that.

I considered implementing -B, but I was afraid it would conflict with
some wrapped program option. Maybe there's a way around that.

-Andi

  reply	other threads:[~2011-10-29  9:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 23:43 Markus Trippelsdorf
2011-10-28  2:11 ` Andi Kleen
2011-10-28  6:25   ` Markus Trippelsdorf
2011-10-29  9:25     ` Markus Trippelsdorf
2011-10-29 13:01       ` Andi Kleen [this message]
2011-10-28  2:17 ` Joseph S. Myers
2011-10-28  6:51   ` Markus Trippelsdorf
2011-10-28 15:51     ` Joseph S. Myers
2011-10-28 16:07       ` Markus Trippelsdorf
2011-10-28  9:04 ` Rainer Orth
2011-10-28 14:17   ` Ian Lance Taylor
2011-10-28 18:21   ` Matthias Klose
2011-10-28 18:01 ` Andreas Tobler
2011-10-31 15:01 ` Rainer Orth
2011-10-31 19:21   ` Ian Lance Taylor
2011-10-31 21:39 ` v2[PATCH] " Markus Trippelsdorf
2011-10-31 21:47   ` [PATCH] Use gcc's libtool in libgo Markus Trippelsdorf
2011-11-01 15:19   ` v2[PATCH] update to libtool-2.4.2 and regenerate Gerald Pfeifer

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=20111029090345.GB14103@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=markus@trippelsdorf.de \
    /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).