* boost archive used for testing
@ 2003-04-02 13:50 Gerald Pfeifer
2003-04-02 17:57 ` Janis Johnson
0 siblings, 1 reply; 6+ messages in thread
From: Gerald Pfeifer @ 2003-04-02 13:50 UTC (permalink / raw)
To: gcc; +Cc: Janis Johnson
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?
(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?)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: boost archive used for testing
2003-04-02 13:50 boost archive used for testing Gerald Pfeifer
@ 2003-04-02 17:57 ` Janis Johnson
2003-04-02 20:14 ` Janis Johnson
2003-04-02 20:45 ` Lars Gullik Bjønnes
0 siblings, 2 replies; 6+ messages in thread
From: Janis Johnson @ 2003-04-02 17:57 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: gcc, Janis Johnson
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: boost archive used for testing
2003-04-02 17:57 ` Janis Johnson
@ 2003-04-02 20:14 ` Janis Johnson
2003-04-02 20:46 ` Gerald Pfeifer
2003-04-02 20:45 ` Lars Gullik Bjønnes
1 sibling, 1 reply; 6+ messages in thread
From: Janis Johnson @ 2003-04-02 20:14 UTC (permalink / raw)
To: Janis Johnson; +Cc: Gerald Pfeifer, gcc
On Wed, Apr 02, 2003 at 09:16:39AM -0800, Janis Johnson wrote:
> If an app listed among the
> release criteria doesn't have a build and test guide, we can remove
> it until someone provides one.
On second thought, this isn't a great idea, even though it might
encourage development of more build and test guides.
If an app that is part of the release criteria has a build and test
guide then links to it can be in the build and test guide; otherwise
they can be in the table in the release criteria.
Janis
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: boost archive used for testing
2003-04-02 20:14 ` Janis Johnson
@ 2003-04-02 20:46 ` Gerald Pfeifer
2003-04-02 21:34 ` Janis Johnson
0 siblings, 1 reply; 6+ messages in thread
From: Gerald Pfeifer @ 2003-04-02 20:46 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc
On Wed, 2 Apr 2003, Janis Johnson wrote:
> If an app that is part of the release criteria has a build and test
> guide then links to it can be in the build and test guide; otherwise
> they can be in the table in the release criteria.
Yes, that sounds like a good plan! (Are you going to implement it?
If not, I'll try to handle it after the weekend...)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: boost archive used for testing
2003-04-02 20:46 ` Gerald Pfeifer
@ 2003-04-02 21:34 ` Janis Johnson
0 siblings, 0 replies; 6+ messages in thread
From: Janis Johnson @ 2003-04-02 21:34 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: Janis Johnson, gcc
On Wed, Apr 02, 2003 at 09:27:12PM +0200, Gerald Pfeifer wrote:
> On Wed, 2 Apr 2003, Janis Johnson wrote:
> > If an app that is part of the release criteria has a build and test
> > guide then links to it can be in the build and test guide; otherwise
> > they can be in the table in the release criteria.
>
> Yes, that sounds like a good plan! (Are you going to implement it?
> If not, I'll try to handle it after the weekend...)
Yes, I'll make the changes, but I'd like you to review them before
I commit them.
Janis
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: boost archive used for testing
2003-04-02 17:57 ` Janis Johnson
2003-04-02 20:14 ` Janis Johnson
@ 2003-04-02 20:45 ` Lars Gullik Bjønnes
1 sibling, 0 replies; 6+ messages in thread
From: Lars Gullik Bjønnes @ 2003-04-02 20:45 UTC (permalink / raw)
To: Janis Johnson; +Cc: Gerald Pfeifer, gcc
Janis Johnson <janis187@us.ibm.com> writes:
| 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 last released one, 1.30.0 currently.
--
Lgb
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-04-02 20:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-02 13:50 boost archive used for testing Gerald Pfeifer
2003-04-02 17:57 ` Janis Johnson
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
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).