Testing 3.1 g++ applications on cygwin

Testing 3.1 g++ applications on cygwin

[Billinghurst, David (CRTS)]

I have built and tested blitz++, boost and MTL using 3.1 prerelease on cygwin.

The results are pretty good.  The few failures seem to be application 
porting/configuration issues rather than compiler problems.
 - boost had one testsuite failure due to missing wchar support
   (A few modules didn't build, but aren't tested) 
 - the MTL test harness spat a few warnings (and ran out of memory)
 - Blitz++ was fine after the patch

I am working through the list of applications - POOMA still has me bluffed.

Re: Testing 3.1 g++ applications on cygwin

[Janis Johnson]

On Fri, Apr 26, 2002 at 04:16:59PM +1000, Billinghurst, David (CRTS) wrote:
> I have built and tested blitz++, boost and MTL using 3.1 prerelease on cygwin.
> 
> The results are pretty good.  The few failures seem to be application 
> porting/configuration issues rather than compiler problems.
>  - boost had one testsuite failure due to missing wchar support
>    (A few modules didn't build, but aren't tested) 
>  - the MTL test harness spat a few warnings (and ran out of memory)
>  - Blitz++ was fine after the patch
> 
> I am working through the list of applications - POOMA still has me bluffed.

If you run into more things in the build and test guides that need
updates, please point them out (or supply patches!).  Also, consider
providing build and test guides for the apps that don't have them yet,
to make it easier for others to test with these packages.

Somewhere out there is a tarball for POOMA with changes to make it
easier to use for GCC testing, and somewhere else is a Perl script to
build and test it.  It sure would be nice if they were linked from the
POOMA build and test guide.

Janis

Re: Testing 3.1 g++ applications on cygwin

[Gerald Pfeifer]

On Fri, 26 Apr 2002, Janis Johnson wrote:
> If you run into more things in the build and test guides that need
> updates, please point them out (or supply patches!).

Seconded.

> Somewhere out there is a tarball for POOMA with changes to make it
> easier to use for GCC testing, and somewhere else is a Perl script to
> build and test it.  It sure would be nice if they were linked from the
> POOMA build and test guide.

ftp://gcc.gnu.org/pub/gcc/infrastructure/pooma-gcc.tar.gz is linked
from http://gcc.gnu.org/gcc-3.1/criteria.html.

Paolo Carlini <pcarlini@unitus.it> also provided an update for
the testing-pooma.html page there.

Are we still missing something?

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

Re: Testing 3.1 g++ applications on cygwin

[Janis Johnson]

On Fri, Apr 26, 2002 at 05:27:22PM +0200, Gerald Pfeifer wrote:
> On Fri, 26 Apr 2002, Janis Johnson wrote:
> > If you run into more things in the build and test guides that need
> > updates, please point them out (or supply patches!).
> 
> Seconded.
> 
> > Somewhere out there is a tarball for POOMA with changes to make it
> > easier to use for GCC testing, and somewhere else is a Perl script to
> > build and test it.  It sure would be nice if they were linked from the
> > POOMA build and test guide.
> 
> ftp://gcc.gnu.org/pub/gcc/infrastructure/pooma-gcc.tar.gz is linked
> from http://gcc.gnu.org/gcc-3.1/criteria.html.
> 
> Paolo Carlini <pcarlini@unitus.it> also provided an update for
> the testing-pooma.html page there.
> 
> Are we still missing something?

Sorry, I was bitten by an old cached copy of criteria.html.  The tarball
is indeed linked, it exists where it's supposed to, and it includes the
script tester.pl.

Janis

Re: Testing 3.1 g++ applications on cygwin

[Janis Johnson]

On Fri, Apr 26, 2002 at 09:17:12AM -0700, Janis Johnson wrote:
> On Fri, Apr 26, 2002 at 05:27:22PM +0200, Gerald Pfeifer wrote:
> > On Fri, 26 Apr 2002, Janis Johnson wrote:
> > > If you run into more things in the build and test guides that need
> > > updates, please point them out (or supply patches!).
> > 
> > Seconded.
> > 
> > > Somewhere out there is a tarball for POOMA with changes to make it
> > > easier to use for GCC testing, and somewhere else is a Perl script to
> > > build and test it.  It sure would be nice if they were linked from the
> > > POOMA build and test guide.
> > 
> > ftp://gcc.gnu.org/pub/gcc/infrastructure/pooma-gcc.tar.gz is linked
> > from http://gcc.gnu.org/gcc-3.1/criteria.html.
> > 
> > Paolo Carlini <pcarlini@unitus.it> also provided an update for
> > the testing-pooma.html page there.
> > 
> > Are we still missing something?
> 
> Sorry, I was bitten by an old cached copy of criteria.html.  The tarball
> is indeed linked, it exists where it's supposed to, and it includes the
> script tester.pl.

I tried building POOMA on ia64-unknown-linux-gnu and i686-pc-linux-gnu
and had configuration problems on both of them.  Would someone like to
see my log files?

Janis

Re: Testing 3.1 g++ applications on cygwin

[Peter Schmid]

I test pooma gcc on a regular basis. I did not encounter a problem since
May 2001. But I am using the original pooma-gcc distribution
with two patches of mine applied, otherwise configuring does not work.

Maybe applying the following patchset makes a difference:
http://gcc.gnu.org/ml/gcc/2001-04/msg01020.html

Hope this helps, if not could you please post your log file.

Peter Schmid

Re: Testing 3.1 g++ applications on cygwin

[Janis Johnson]

On Fri, Apr 26, 2002 at 08:37:04PM +0200, Peter Schmid wrote:
> I test pooma gcc on a regular basis. I did not encounter a problem since
> May 2001. But I am using the original pooma-gcc distribution
> with two patches of mine applied, otherwise configuring does not work.
> 
> Maybe applying the following patchset makes a difference:
> http://gcc.gnu.org/ml/gcc/2001-04/msg01020.html
> 
> Hope this helps, if not could you please post your log file.
> 
> Peter Schmid

Thanks, I applied that patch to pooma-gcc and it's chugging along now.

Gerald, how about this for gcc-3.1/testing-pooma.html?  The formatting
surrounding the patch code is highly questionable, so feel free to fix
it or tell me how to do it properly.

On the other hand, perhaps someone can rebuild the pooma-gcc tarball,
fixing this and also the copyright in testing.pl.

Janis

Index: testing-pooma.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/testing-pooma.html,v
retrieving revision 1.2
diff -u -p -r1.2 testing-pooma.html
--- testing-pooma.html	18 Apr 2002 20:27:38 -0000	1.2
+++ testing-pooma.html	26 Apr 2002 20:59:39 -0000
@@ -28,6 +28,36 @@ programs, and run the examples, use:</p>
     <li><code>cd pooma-gcc</code></li>
     </ul>
 </li>
+<li>Apply this patch:
+    <ul>
+    <li><code>patch -b -p0 &lt;&lt; END_OF_PATCH
+        <pre>
+--- tester.pl.orig      Fri Apr 26 11:06:30 2002
++++ tester.pl   Fri Apr 26 11:06:57 2002
+@@ -111,7 +111,7 @@ while (<VARIABLETEMPLATE>)
+ }
+ close (VARIABLES);
+ die ("Failed to finish writing the shared variables file.") if $?;
+-close (VARIABLE-TEMPLATE);
++close (VARIABLETEMPLATE);
+ die ("Failed to finish reading the shared variables template file.") if $?;
+
+ ######################################################################
+--- config/Shared/tail.mk.orig  Fri Apr 26 13:26:20 2002
++++ config/Shared/tail.mk       Fri Apr 26 13:25:57 2002
+@@ -110,7 +110,7 @@ endif
+ include $(SHARED_ROOT)/rules.mk
+
+ # Include (if it exists) the dependency file.
+--include $(LIBRARY_ROOT)/depend.mk
++#-include $(LIBRARY_ROOT)/depend.mk
+
+
+ # ACL:rcsinfo
+END_OF_PATCH
+    </pre></code></li>
+    </ul>
+</li>
 </ul>
 
 

Re: Testing 3.1 g++ applications on cygwin

[Gerald Pfeifer]

On Fri, 26 Apr 2002, Janis Johnson wrote:
> Gerald, how about this for gcc-3.1/testing-pooma.html?  The formatting
> surrounding the patch code is highly questionable, so feel free to fix
> it or tell me how to do it properly.
>
> On the other hand, perhaps someone can rebuild the pooma-gcc tarball,
> fixing this and also the copyright in testing.pl.

Yeah, that certainly would be preferrable.  I'm extremely short of time
until (at least Monday), but if you mail me an updated tarball or a patch
to apply, I'll put up a fresh tarball on gcc.gnu.org ASAP.

Gerald

Re: Testing 3.1 g++ applications on cygwin

[Janis Johnson]

On Fri, Apr 26, 2002 at 11:12:19PM +0200, Gerald Pfeifer wrote:
> On Fri, 26 Apr 2002, Janis Johnson wrote:
> > Gerald, how about this for gcc-3.1/testing-pooma.html?  The formatting
> > surrounding the patch code is highly questionable, so feel free to fix
> > it or tell me how to do it properly.
> >
> > On the other hand, perhaps someone can rebuild the pooma-gcc tarball,
> > fixing this and also the copyright in testing.pl.
> 
> Yeah, that certainly would be preferrable.  I'm extremely short of time
> until (at least Monday), but if you mail me an updated tarball or a patch
> to apply, I'll put up a fresh tarball on gcc.gnu.org ASAP.
> 
> Gerald

IBM policies don't allow me to make changes to a tarball and and make it
available again, but it should be easy for someone else to do this for
Gerald: just make the two small changes shown in my previous mail (picked
up from old mail from Peter Schmid) and remove the copyright message in
tester.pl; Mark Mitchell placed that script in the public domain in
http://gcc.gnu.org/ml/gcc-patches/2002-04/msg01042.html.

Janis

Re: Testing 3.1 g++ applications on cygwin

[Paolo Carlini]

Janis Johnson wrote:

>IBM policies don't allow me to make changes to a tarball and and make it
>available again, but it should be easy for someone else to do this for
>Gerald: just make the two small changes shown in my previous mail (picked
>up from old mail from Peter Schmid) and remove the copyright message in
>tester.pl; Mark Mitchell placed that script in the public domain in
>http://gcc.gnu.org/ml/gcc-patches/2002-04/msg01042.html.
>

Ok. I will do this momentarily...

Ciao, Paolo.

Re: Testing 3.1 g++ applications on cygwin

[Gerald Pfeifer]

On Sat, 27 Apr 2002, Paolo Carlini wrote:
> Ok. I will do this momentarily...

Thanks! The updated tarball is already on ftp://gcc.gnu.org.

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/