public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: schwab@suse.de, gcc-patches@gcc.gnu.org, libstdc++-digest@gcc.gnu.org
Subject: Re: Patch to update libtool in GCC and binutils trees
Date: Thu, 05 Apr 2007 06:58:00 -0000	[thread overview]
Message-ID: <orabxn1fcb.fsf@free.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200703292205.PAA19224@hpsje.cup.hp.com> (Steve Ellcey's message of "Thu\, 29 Mar 2007 15\:05\:56 -0700 \(PDT\)")

On Mar 29, 2007, Steve Ellcey <sje@cup.hp.com> wrote:

> Does anyone have a better way
> to handle this test in the libstdc++-v3 configure file?

There should be a shell variable holding the right value, with
ltconfig fully integrated into the main configure script.

> Can I just check the enable_shared variable instead?

Most likely.  I don't have your patch handy any more, but if you could
check that enable_shared is what makes to the libtool script, that
later outputs "enable shared", then yes.  There might be per-language
settings.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

  reply	other threads:[~2007-04-05  6:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 17:12 Steve Ellcey
2007-03-26 16:58 ` Steve Ellcey
2007-03-26 18:01   ` Paolo Bonzini
2007-03-29 16:58     ` Steve Ellcey
2007-03-29 17:05       ` Andreas Schwab
2007-03-29 19:25         ` Steve Ellcey
2007-03-29 23:01           ` Steve Ellcey
2007-04-05  6:58             ` Alexandre Oliva [this message]
2007-03-30  7:24 ` Ben Elliston
  -- strict thread matches above, loose matches on Subject: below --
2007-04-05 22:21 Steve Ellcey
2007-04-05 22:54 ` Alexandre Oliva
2007-04-06 16:24   ` Steve Ellcey
2007-04-06 16:59     ` Benjamin Kosnik
     [not found] <200703281744.l2SHin837088@makai.watson.ibm.com>
     [not found] ` <200703282231.PAA13113@hpsje.cup.hp.com>
2007-03-30 10:24   ` François-Xavier Coudert
2007-03-30 11:56     ` François-Xavier Coudert
2007-04-02 11:21     ` Ralf Wildenhues
2007-04-02 11:25       ` Paolo Bonzini
2007-03-30  4:16 Charles Wilson
2007-03-30 18:29 ` Steve Ellcey
2007-04-02 11:22   ` Ralf Wildenhues
2007-04-02 21:05     ` Steve Ellcey
2007-04-05  7:06       ` Alexandre Oliva
2007-04-02 11:19 ` Ralf Wildenhues
2007-03-23  9:45 Paolo Bonzini
     [not found] ` <200703231550.IAA20980@hpsje.cup.hp.com>
2007-03-23 16:37   ` François-Xavier Coudert
2007-03-23  0:10 FX Coudert
2007-03-22 21:48 Steve Ellcey

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=orabxn1fcb.fsf@free.oliva.athome.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++-digest@gcc.gnu.org \
    --cc=schwab@suse.de \
    --cc=sje@cup.hp.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).