From: Phil Edwards <pedwards@disaster.jaj.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: aoliva@redhat.com, gcc@gcc.gnu.org
Subject: Re: libstdc++v3 configuration
Date: Thu, 22 Nov 2001 08:37:00 -0000 [thread overview]
Message-ID: <20011129205717.A26811@disaster.jaj.com> (raw)
In-Reply-To: <10111300057.AA23535@vlsi1.ultra.nyu.edu>; from kenner@vlsi1.ultra.nyu.edu on Thu, Nov 29, 2001 at 07:57:33PM -0500
On Thu, Nov 29, 2001 at 07:57:33PM -0500, Richard Kenner wrote:
> Risking pointing out the obvious: do you have
> libstdc++-v3/po/Makefile.in in your source tree?
>
> No. I wonder why not, though. I do "cvs update" ...
Either contrib/gcc_update or "cvs update -Pd" is what you want, I think.
> But there's still the nearly-two-hour configure time.
In the mean time, you might consider saving select bits of config.cache
and then using them to prime the cache on subsequent runs.
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
WARNING: multiple messages have this Message-ID
From: Phil Edwards <pedwards@disaster.jaj.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: aoliva@redhat.com, gcc@gcc.gnu.org
Subject: Re: libstdc++v3 configuration
Date: Thu, 29 Nov 2001 17:54:00 -0000 [thread overview]
Message-ID: <20011129205717.A26811@disaster.jaj.com> (raw)
Message-ID: <20011129175400.VhqPi-bGIuUwDe1iXVQETPMmyKrtBKjr-k6e3n2NwXQ@z> (raw)
In-Reply-To: <10111300057.AA23535@vlsi1.ultra.nyu.edu>
On Thu, Nov 29, 2001 at 07:57:33PM -0500, Richard Kenner wrote:
> Risking pointing out the obvious: do you have
> libstdc++-v3/po/Makefile.in in your source tree?
>
> No. I wonder why not, though. I do "cvs update" ...
Either contrib/gcc_update or "cvs update -Pd" is what you want, I think.
> But there's still the nearly-two-hour configure time.
In the mean time, you might consider saving select bits of config.cache
and then using them to prime the cache on subsequent runs.
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next prev parent reply other threads:[~2001-11-30 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 5:03 Richard Kenner
2001-11-22 8:37 ` Phil Edwards [this message]
2001-11-29 17:54 ` Phil Edwards
2001-11-29 17:03 ` Richard Kenner
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 14:26 Richard Kenner
2001-11-21 15:03 ` Alexandre Oliva
2001-11-29 7:59 ` Alexandre Oliva
2001-11-29 6:31 ` Richard Kenner
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=20011129205717.A26811@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).