From: Mark Mitchell <mark@codesourcery.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.4.2 Release Candidate Available
Date: Tue, 31 Aug 2004 04:51:00 -0000 [thread overview]
Message-ID: <4133FCEB.9070708@codesourcery.com> (raw)
In-Reply-To: <4133F936.nailGYJ1ZALT3@mindspring.com>
Michael Chastain wrote:
>[This is a weird time for me to be awake, but I'm under a bit of stress
> right now, and it soothes me to do this ...]
>
>Mark Mitchell writes:
>
>
>>Please perform testing by building directly from these sources,
>>not from CVS, so that we can test our packaging.
>>
>>
>
>Okay. I am doing:
>
> foreach machine $(hp_test_drive_cluster)
> mkdir build install ; cd build
> /foo/bar/configure --prefix=/foo/bar/install
> make bootstrap
> make install
> done
>
>I've run into several bootstrap errors, which I shall proceed to
>file PR's for.
>
>
Thanks. If these are funny old HP machines, we'll likely ignore the
problems, but it will be good to have the reports. :-)
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com
next prev parent reply other threads:[~2004-08-31 4:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 4:28 Michael Chastain
2004-08-31 4:51 ` Mark Mitchell [this message]
2004-08-31 4:59 ` Michael Chastain
2004-08-31 16:56 ` Joe Buck
[not found] ` <20040831165229.A1723@synopsys.com>
2004-09-01 5:21 ` Christian Joensson
2004-09-01 5:24 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 18:43 Harald Dunkel
2004-08-31 18:53 ` Daniel Jacobowitz
2004-08-31 22:01 ` Harald Dunkel
2004-08-29 23:17 Mark Mitchell
2004-08-31 17:57 ` Janis Johnson
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=4133FCEB.9070708@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=mec.gnu@mindspring.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).