From: Janis Johnson <janis187@us.ibm.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org, Janis Johnson <janis187@us.ibm.com>
Subject: Re: boost archive used for testing
Date: Wed, 02 Apr 2003 17:57:00 -0000 [thread overview]
Message-ID: <20030402091639.A1390@us.ibm.com> (raw)
In-Reply-To: <Pine.BSF.4.53.0304021318100.14072@acrux.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Wed, Apr 02, 2003 at 01:19:49PM +0200
On Wed, Apr 02, 2003 at 01:19:49PM +0200, Gerald Pfeifer wrote:
> On a couple of pages we have links to
> http://www.boost.org/boost_all.tar.gz
> which doesn't exist any longer.
>
> How should we resolve this?
There are several versions and formats to choose from at SourceForge.
Should we recommend a particular version for GCC integration testing
and if so, which one? (That question is for people familiar with
Boost.)
The other packages ought to be updated as well. A few days ago I built
the recommended version of Blitz++, which gets tons of warnings with 3.3
on powerpc64-linux but passes all tests. A more recent version doesn't
get warnings and also passes all tests. I haven't tried it with
mainline, but some of these older versions might not even compile with
the new C++ parser. That was true of FTensor, due to questionable code
in FTensor (according to Walter Landry) rather than problems with the
new parser.
> (Ideally, we'd really have just one link to every external package used
> for testing. Do you have a good idea on how to solve that, Janis?)
We can move links to particular application packages down to the
build and test guides; that goes for the tarball and also for the
link to information about the package. If an app listed among the
release criteria doesn't have a build and test guide, we can remove
it until someone provides one. I had meant to remove the build and
test guides from gcc-3.1 and redirect those to the ones in the
testing directory; I'll do that.
Janis
next prev parent reply other threads:[~2003-04-02 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 13:50 Gerald Pfeifer
2003-04-02 17:57 ` Janis Johnson [this message]
2003-04-02 20:14 ` Janis Johnson
2003-04-02 20:46 ` Gerald Pfeifer
2003-04-02 21:34 ` Janis Johnson
2003-04-02 20:45 ` Lars Gullik Bjønnes
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=20030402091639.A1390@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).