public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Re: A config patch
Date: Wed, 27 Aug 1997 16:44:42 -0000	[thread overview]
Message-ID: <199708271526.LAA03697@subrogation.cygnus.com> (raw)
Message-ID: <19970827164442.We8eTv_7VnQ2rNU6p0Ort8R0hRDN2NAeGIQitxljIb8@z> (raw)
In-Reply-To: A config patch

  In message <199708270841.BAA10195@rtl.cygnus.com>you write:
  > > There's no reference to these files in the toplevel configure.in;
  > > therefore, they will never be used.
  > 
  > I forget the mechanism, but they get pulled via --enable-shared
  > in to attempt to build eg libiberty shared.
Oh, I see it.  You learn something new every day.

What I still don't see is the point behind setting PICFLAG on this
target -- yes, the if [-z "$PICFLAG"] test will now succeed, but,
least least for libiberty, I don't see benefit.

jeff

             reply	other threads:[~1997-08-27 16:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-27 16:44 Ian Lance Taylor [this message]
1997-08-27 16:44 ` Jeffrey A Law
1997-08-27 16:44 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1997-08-28  8:21 HAVE_STDLIB_H Craig Burley
1997-08-28 14:34 ` maintainer mode [was: Re: Building of generated parser files] Gary V Vaughan
1997-08-27 16:44 Kaveh R. Ghazi
1997-08-27  8:07 Some Linux patches Richard Henderson
1997-08-27 12:08 ` maintainer mode [was: Re: Building of generated parser files] Samuel Tardieu
1997-08-27  0:20 Richard Stallman
1997-08-26 21:22 Kaveh R. Ghazi
1997-08-26 20:50 Test run and a question Joe Buck
1997-08-26 20:56 ` maintainer mode [was: Re: Building of generated parser files] Alexandre Oliva
1997-08-26 20:18 Fred Fish
1997-08-26 20:18 Ian Lance Taylor
1997-08-26 19:15 Richard Stallman
1997-08-26 15:53 Ian Lance Taylor
1997-08-26 14:34 Some Haifa scheduler bugs Bernd Schmidt
1997-08-26 15:29 ` maintainer mode [was: Re: Building of generated parser files] François Pinard

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=199708271526.LAA03697@subrogation.cygnus.com \
    --to=law@hurl.cygnus.com \
    --cc=egcs@cygnus.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).