Re: [boost] Call for regression test volunteers
> OK, found the problem. Apparantly on my HP machine I should leave out the > CC=gcc. BTW John I made sure that no command-line options are needed on the > command-line to compile jamboost so I certainly prefer to remove the > "CC=gcc". Is that OK ? OK, I'll put a commented out # export CC=gcc before it, as a reminder that some people may need this. John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Thursday 09 January 2003 22:37, Rene Rivera wrote: > [2003-01-09] David Abrahams wrote: > OK that seems like a good idea. I'll add generic Unix cc toolset for > building bjam. tried it but : harry:/home/tk/boost/boost/tools/build/jam_src >./build.sh ### ### Could not find a suitable toolset. ### ### You can specify the toolset as the argument, i.e.: ### ./build.sh gcc ### ### Toolsets supported by this script are: ### acc, como, darwin, gcc, intel-linux, kcc, kylix, mipspro, ### sunpro, tru64cxx, vacpp ### A special toolset; cc, is available which is used as a fallback ### when a more specific toolset is not available and the cc command ### detected. ### and when doing ./build.sh cc harry:/home/tk/boost/boost/tools/build/jam_src >./build.sh cc ### ### Using 'cc' toolset. ### rm -rf bootstrap.cc mkdir bootstrap.cc cc -o bootstrap.cc/jam0 command.c compile.c execnt.c execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c command.c: compile.c: execnt.c: execunix.c: execvms.c: expand.c: filent.c: fileos2.c: fileunix.c: filevms.c: glob.c: hash.c: hdrmacro.c: headers.c: jam.c: jambase.c: jamgram.c: Warning 612: "y.tab.c", line 521 # Label 'yynewerror' has no uses. yynewerror: ^^^ Warning 612: "y.tab.c", line 526 # Label 'yyerrlab' has no uses. yyerrlab: ^ lists.c: make.c: make1.c: newstr.c: option.c: parse.c: pathunix.c: pathvms.c: regexp.c: rules.c: scan.c: search.c: subst.c: timestamp.c: variable.c: modules.c: strings.c: filesys.c: builtins.c: pwd.c: ./bootstrap.cc/jam0 -f build.jam --toolset=cc --toolset-root= build.jam:103: in module scope *** argument error * rule toolset ( name command : opt.out + : opt.define + : release-flags * : debug-flags * : linklibs * ) * called with: ( metrowerks : -o : -D : -subsystem console -runtime staticsingle -opt full -inline auto -inline level=8 : -subsystem console -runtime staticsingle -O0 -inline off ) * missing argument command build.jam:39:see definition of rule 'toolset' being called This is probably because yacc is still used > > But for aCC, can one of you tell what the output of 'uname' is. At least I > can test that in this case. harry:/home/tk/boost/boost/tools/build/jam_src >uname -a HP-UX harry B.11.22 U ia64 1850224727 unlimited-user license harry:/home/tk/boost/boost/tools/build/jam_src >uname HP-UX ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Thursday 09 January 2003 22:40, Rene Rivera wrote: > [2003-01-09] Toon Knapen wrote: > >Anyway, to compile jam_src you can use cc (with the -Ae option though) as > >you can see in the Jambase. > > PS. What does the -Ae option do? from the man pages of aCC/cc : -AeIn aC++, invokes aCC as an ANSI-C compiler, with additional support for HP-C language extensions. Refer to the HP-C compiler documentation for details of the HP-C language extensions. In ANSI C, this is the default Extended ANSI mode. Same as -Aa -D_HPUX_SOURCE +e. This would define the names (macros and typedefs) provided by the HP-UX Operating System and, in addition, allows extensions such as C99 features newly implemented in this release (complex and imaginary data types, STDC pragmas), $ characters in identifier names, sized enums, and sized bit-fields, and 64-bit integral types. Additional extensions may ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] Rene Rivera wrote: >[2003-01-09] John Maddock wrote: > >> >>> John would you mind if I "improve" on the script. I'd like to run it on >my >>> OpenBSD server to help out. But I would have to add fetching of Boost >from >>> CVS as a step. -- I could document it more as I do this ;-) >> >>No absolutely go for it! >> >>I guess there really should be a extra step at the end as well to upload >the >>resulting table. Actually I did wonder if these steps would be better as a >>separate script (that calls mine), to cater for off-line testers as well as >>on-line ones... > >I'm changing it so it is still usefull for both uses. I think a single >script make for a better interface in this case. It's much easier to point >people to a single script and say "Here, configure, and run it!" OK, done with the changes. New script is in CVS. Ran my first full regression test sequence for OpenBSD with GCC 3.2. I'll put the results up for OpenBSD when the tests run again in my normal nightly script cycle. I'll add GCC 3.0.x and 2.95.3 soon. And STLport variants when I get that compiled. Are there any other compilers available for OpenBSD other than gcc? -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
RE: [boost] Call for regression test volunteers
At 03:44 AM 1/9/2003, Darryl Green wrote: >I don't know what the restrictions are but it might be worth looking at >http://testdrive.hp.com which claims to offer alpha, itanium, PA-RISC, >StrongARM and x86 systems running BSD, HP-UX, Linux, OpenVMS and Tru64: Interesting, but it looks more oriented to quick tests than something like running the full Boost regression tests on a regular basis. Still, they might consider Boost a special case because Boost represents a whole community of developers rather than just one person or company. If someone wants to try to work with testdrive.hp, maybe give it a try and report back your experiences. --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
At 09:40 PM 1/9/2003, Toon Knapen wrote: >On Thursday 09 January 2003 14:51, Beman Dawes wrote: >> At 04:48 AM 1/9/2003, Toon Knapen wrote: >> >I'm working on the port to HPUX (recently I've send a few msg's out on >> >this) but have trouble compiling the regression-reporting tools. >> >Already patched a few things in MPL but now the filesystem lib is >> >causing headeaches. If you and/or Jens (did previous ports to HP) >> >could help me out ... ? >> >> Toon, let me know what about the filesystem is causing problems. It is >> supposed to be deliberately straightforward code to minimize porting >> problems. > >I know but the problem reports soth. like (I'm at home so I can't give you >the actual output now) "namespace nesting too deep". IMO it's not an error >in the fslib but I just have to find some workaround to prevent the error >from occuring. I'll keep you informed. Try GCC? Good luck, and do let us know what happens. --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
At 03:29 PM 1/9/2003, Rene Rivera wrote: >Speaking of that... What are the requirements for getting the filesystem >code to compile? I'm trying to get GCC2.95.3 on OpenBSD to compile it for >the regression testing. > >Is there a specific version of GCC required? Or would using STLport be >sufficient? The only other Boost code Filesystem uses is a couple of the smart pointers plus iterator_adaptors.hpp. It normally doesn't stress a compiler at all, other than maybe iterator_adaptors.hpp. If push came to shove I could remove the use of iterator_adaptors.hpp. But I would be surprised if even older versions of GCC had problems with filesystem code. The other possibility for any system having compiler problems would be to download a recent version of GCC. I'm about as makefile averse as anyone, but must say that building gcc is painless even on Windows. Presumably it is even easier on UNIX systems. There are also binaries available for many systems. That way you will have at least one decent compiler and library available. --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] David Abrahams wrote: >Toon Knapen <[EMAIL PROTECTED]> writes: > >> On Thursday 09 January 2003 12:12, Rene Rivera wrote: >>> It's doesn't because I haven't had time to add it since the toolset >>> appeared in Boost.Build ;-) I'll try and add ASAP. ... Question on this... >>> Is it a possibility to install only the C compiler (cc) without the C++ >>> compiler (aCC)? I'm asking to see if I can use the presense of "aCC" as an >>> indicator that it's all installed. >> >> I guess cc is installed by default (like on all unices) and aCC is a >> commerical product. So cc is always there and aCC is'nt. >> >> Anyway, to compile jam_src you can use cc (with the -Ae option though) as >> you can see in the Jambase. > >Yeah, I think on Unix, defaulting to cc unless the script knows better >is a god idea. It would've prevented this issue with getting aCC to >build it in the first place. That's what the Perforce makefile does, >too. OK that seems like a good idea. I'll add generic Unix cc toolset for building bjam. But for aCC, can one of you tell what the output of 'uname' is. At least I can test that in this case. -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] Toon Knapen wrote: >Anyway, to compile jam_src you can use cc (with the -Ae option though) as >you can see in the Jambase. PS. What does the -Ae option do? -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
Toon Knapen <[EMAIL PROTECTED]> writes: > On Thursday 09 January 2003 12:12, Rene Rivera wrote: >> It's doesn't because I haven't had time to add it since the toolset >> appeared in Boost.Build ;-) I'll try and add ASAP. ... Question on this... >> Is it a possibility to install only the C compiler (cc) without the C++ >> compiler (aCC)? I'm asking to see if I can use the presense of "aCC" as an >> indicator that it's all installed. > > I guess cc is installed by default (like on all unices) and aCC is a > commerical product. So cc is always there and aCC is'nt. > > Anyway, to compile jam_src you can use cc (with the -Ae option though) as > you can see in the Jambase. Yeah, I think on Unix, defaulting to cc unless the script knows better is a god idea. It would've prevented this issue with getting aCC to build it in the first place. That's what the Perforce makefile does, too. -- David Abrahams [EMAIL PROTECTED] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
Toon Knapen <[EMAIL PROTECTED]> writes: > On Thursday 09 January 2003 14:51, Beman Dawes wrote: >> At 04:48 AM 1/9/2003, Toon Knapen wrote: >> >I'm working on the port to HPUX (recently I've send a few msg's out on >> >this) but have trouble compiling the regression-reporting tools. >> >Already patched a few things in MPL but now the filesystem lib is >> >causing headeaches. If you and/or Jens (did previous ports to HP) >> >could help me out ... ? >> >> Toon, let me know what about the filesystem is causing problems. It is >> supposed to be deliberately straightforward code to minimize porting >> problems. > > I know but the problem reports soth. like (I'm at home so I can't give you > the actual output now) "namespace nesting too deep". IMO it's not an error in > the fslib but I just have to find some workaround to prevent the error from > occuring. I'll keep you informed. Yeah, the abysmal error reports from that compiler make it very hard. That's one reason I was suggesting you start with simpler libraries, like type_traits, so you can cut the examples down until they stop failing. -- David Abrahams [EMAIL PROTECTED] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Thursday 09 January 2003 14:51, Beman Dawes wrote: > At 04:48 AM 1/9/2003, Toon Knapen wrote: > >I'm working on the port to HPUX (recently I've send a few msg's out on > >this) but have trouble compiling the regression-reporting tools. > >Already patched a few things in MPL but now the filesystem lib is > >causing headeaches. If you and/or Jens (did previous ports to HP) > >could help me out ... ? > > Toon, let me know what about the filesystem is causing problems. It is > supposed to be deliberately straightforward code to minimize porting > problems. I know but the problem reports soth. like (I'm at home so I can't give you the actual output now) "namespace nesting too deep". IMO it's not an error in the fslib but I just have to find some workaround to prevent the error from occuring. I'll keep you informed. t ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Thursday 09 January 2003 12:12, Rene Rivera wrote: > It's doesn't because I haven't had time to add it since the toolset > appeared in Boost.Build ;-) I'll try and add ASAP. ... Question on this... > Is it a possibility to install only the C compiler (cc) without the C++ > compiler (aCC)? I'm asking to see if I can use the presense of "aCC" as an > indicator that it's all installed. I guess cc is installed by default (like on all unices) and aCC is a commerical product. So cc is always there and aCC is'nt. Anyway, to compile jam_src you can use cc (with the -Ae option though) as you can see in the Jambase. toon ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] Beman Dawes wrote: >At 04:48 AM 1/9/2003, Toon Knapen wrote: > > >I'm working on the port to HPUX (recently I've send a few msg's out on > >this) but have trouble compiling the regression-reporting tools. > >Already patched a few things in MPL but now the filesystem lib is > >causing headeaches. If you and/or Jens (did previous ports to HP) > >could help me out ... ? > >Toon, let me know what about the filesystem is causing problems. It is >supposed to be deliberately straightforward code to minimize porting >problems. Speaking of that... What are the requirements for getting the filesystem code to compile? I'm trying to get GCC2.95.3 on OpenBSD to compile it for the regression testing. Is there a specific version of GCC required? Or would using STLport be sufficient? -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
At 04:48 AM 1/9/2003, Toon Knapen wrote: >I'm working on the port to HPUX (recently I've send a few msg's out on >this) but have trouble compiling the regression-reporting tools. >Already patched a few things in MPL but now the filesystem lib is >causing headeaches. If you and/or Jens (did previous ports to HP) >could help me out ... ? Toon, let me know what about the filesystem is causing problems. It is supposed to be deliberately straightforward code to minimize porting problems. --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] Rene Rivera wrote: >[2003-01-09] David Abrahams wrote: >>No, it means that targets will be placed in the bin subdir. >>However, Rene has put together some new build scripts for bjam. The >>new recommended procedure is: >> >> bash ./build.sh >> >>I know that build.sh starts with #!/bin/sh, but in fact it seems to >>require bash on my machine. My sh doesn't know about 'function'. > >Hmm, I thought I fixed that :-( I'll fix ASAP as I move over to compiling on >OpenBSD as it has a real sh. OK, it's fixed :-) I also added aCC toolset. -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] David Abrahams wrote: >Toon Knapen <[EMAIL PROTECTED]> writes: > >>> I did a bunch of testing on and porting to HP, but I wasn't using >>> filesystem or the post-processing tools. If it's giving you trouble >>> you might consider just using bjam to run tests for a while as you >>> pick off the low-hanging fruit. It might well be that Filesystem is >>> broken because of some simpler library it depends on. >> >> At the moment I'm going for John's suggestion : compile the tools with gcc and >> then proceed with aCC. >> >> I had my own script to do all the work but I figured I might as well >> use/contribute to the script in tools/regression/run_tests.sh. One question >> though, the line : >> >> cd $BOOST_ROOT/tools/build/jam_src && \ >> make CC=gcc YACC="" LOCATE_TARGET=bin >> >> is giving me trouble due to the LOCATE_TARGET. This apparantly makes >> that the sources are searched for in the bin subdir ?! Should'nt it >> be removed ? > >No, it means that targets will be placed in the bin subdir. >However, Rene has put together some new build scripts for bjam. The >new recommended procedure is: > > bash ./build.sh > >I know that build.sh starts with #!/bin/sh, but in fact it seems to >require bash on my machine. My sh doesn't know about 'function'. Hmm, I thought I fixed that :-( I'll fix ASAP as I move over to compiling on OpenBSD as it has a real sh. I'm also changing the test script to the new method. -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] Toon Knapen wrote: >On Thursday 09 January 2003 16:06, David Abrahams wrote: >> > is giving me trouble due to the LOCATE_TARGET. This apparantly makes >> > that the sources are searched for in the bin subdir ?! Should'nt it >> > be removed ? >> >> No, it means that targets will be placed in the bin subdir. > >OK, found the problem. Apparantly on my HP machine I should leave out the >CC=gcc. BTW John I made sure that no command-line options are needed on the >command-line to compile jamboost so I certainly prefer to remove the >"CC=gcc". Is that OK ? > >> However, Rene has put together some new build scripts for bjam. The >> new recommended procedure is: >> >>bash ./build.sh > >Apparantly does not know aCC yet ;( It's doesn't because I haven't had time to add it since the toolset appeared in Boost.Build ;-) I'll try and add ASAP. ... Question on this... Is it a possibility to install only the C compiler (cc) without the C++ compiler (aCC)? I'm asking to see if I can use the presense of "aCC" as an indicator that it's all installed. > But why is it necessary. Had no trouble >recently compiling jam_src with make on all platforms (I know, I should >follow the discussions in the jamboost-ml more closely but so little time;( ? It was necessary for when I built on Win32 with CW, which is why I added a build.bat. And then to make things consistent I also added a build.sh to mirror it. It does have the benefit that it's much easier to use than trying to remember the option to pass to make to compile on each platform. -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-09] John Maddock wrote: > >> John would you mind if I "improve" on the script. I'd like to run it on my >> OpenBSD server to help out. But I would have to add fetching of Boost from >> CVS as a step. -- I could document it more as I do this ;-) > >No absolutely go for it! > >I guess there really should be a extra step at the end as well to upload the >resulting table. Actually I did wonder if these steps would be better as a >separate script (that calls mine), to cater for off-line testers as well as >on-line ones... I'm changing it so it is still usefull for both uses. I think a single script make for a better interface in this case. It's much easier to point people to a single script and say "Here, configure, and run it!" -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Thursday 09 January 2003 16:06, David Abrahams wrote: > > is giving me trouble due to the LOCATE_TARGET. This apparantly makes > > that the sources are searched for in the bin subdir ?! Should'nt it > > be removed ? > > No, it means that targets will be placed in the bin subdir. OK, found the problem. Apparantly on my HP machine I should leave out the CC=gcc. BTW John I made sure that no command-line options are needed on the command-line to compile jamboost so I certainly prefer to remove the "CC=gcc". Is that OK ? > However, Rene has put together some new build scripts for bjam. The > new recommended procedure is: > >bash ./build.sh Apparantly does not know aCC yet ;( But why is it necessary. Had no trouble recently compiling jam_src with make on all platforms (I know, I should follow the discussions in the jamboost-ml more closely but so little time;( ? toon ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
Toon Knapen <[EMAIL PROTECTED]> writes: >> I did a bunch of testing on and porting to HP, but I wasn't using >> filesystem or the post-processing tools. If it's giving you trouble >> you might consider just using bjam to run tests for a while as you >> pick off the low-hanging fruit. It might well be that Filesystem is >> broken because of some simpler library it depends on. > > At the moment I'm going for John's suggestion : compile the tools with gcc and > then proceed with aCC. > > I had my own script to do all the work but I figured I might as well > use/contribute to the script in tools/regression/run_tests.sh. One question > though, the line : > > cd $BOOST_ROOT/tools/build/jam_src && \ > make CC=gcc YACC="" LOCATE_TARGET=bin > > is giving me trouble due to the LOCATE_TARGET. This apparantly makes > that the sources are searched for in the bin subdir ?! Should'nt it > be removed ? No, it means that targets will be placed in the bin subdir. However, Rene has put together some new build scripts for bjam. The new recommended procedure is: bash ./build.sh I know that build.sh starts with #!/bin/sh, but in fact it seems to require bash on my machine. My sh doesn't know about 'function'. -Dave -- David Abrahams [EMAIL PROTECTED] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
> I did a bunch of testing on and porting to HP, but I wasn't using > filesystem or the post-processing tools. If it's giving you trouble > you might consider just using bjam to run tests for a while as you > pick off the low-hanging fruit. It might well be that Filesystem is > broken because of some simpler library it depends on. At the moment I'm going for John's suggestion : compile the tools with gcc and then proceed with aCC. I had my own script to do all the work but I figured I might as well use/contribute to the script in tools/regression/run_tests.sh. One question though, the line : cd $BOOST_ROOT/tools/build/jam_src && \ make CC=gcc YACC="" LOCATE_TARGET=bin is giving me trouble due to the LOCATE_TARGET. This apparantly makes that the sources are searched for in the bin subdir ?! Should'nt it be removed ? toon ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
Toon Knapen <[EMAIL PROTECTED]> writes: > On Wednesday 08 January 2003 17:16, Rene Rivera wrote: >> [2003-01-08] Beman Dawes wrote: >> >At 07:58 AM 1/8/2003, John Maddock wrote: >> > >This is another call for volunteers to come forward to help run the >> > > boost regression tests on more platforms, particularly needed are the >> > >> >commercial >> > >> > >Unix variants (Solaris, HP, SGI Irix etc), but also Free|Net|OpenBSD and >> > >MacOS X. > > I'm working on the port to HPUX (recently I've send a few msg's out on this) > but have trouble compiling the regression-reporting tools. Already patched a > few things in MPL but now the filesystem lib is causing headeaches. If you > and/or Jens (did previous ports to HP) could help me out ... ? I did a bunch of testing on and porting to HP, but I wasn't using filesystem or the post-processing tools. If it's giving you trouble you might consider just using bjam to run tests for a while as you pick off the low-hanging fruit. It might well be that Filesystem is broken because of some simpler library it depends on. -- David Abrahams [EMAIL PROTECTED] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
> John would you mind if I "improve" on the script. I'd like to run it on my > OpenBSD server to help out. But I would have to add fetching of Boost from > CVS as a step. -- I could document it more as I do this ;-) No absolutely go for it! I guess there really should be a extra step at the end as well to upload the resulting table. Actually I did wonder if these steps would be better as a separate script (that calls mine), to cater for off-line testers as well as on-line ones... John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
> Good! This may be useful to some of the compiler suppliers, too. > > Would you be willing to add it to tools/regression? Done. > Just yesterday I committed a simple tools/regression/index.htm file. A > mention with link to the script could go there, and perhaps a bit of > documentation in more/regression.html. At the least, there should be a link > in more/regression.html. Done. > In looking at the script, perhaps it could be made a bit clearer what needs > to be changed to tailor it to a particular system. Or perhaps that could be > done in the docs. Anyhow, this should be a helpful addition. Thanks, I'll try and add more comments as any problems show up. John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
> I'm working on the port to HPUX (recently I've send a few msg's out on this) > but have trouble compiling the regression-reporting tools. Already patched a > few things in MPL but now the filesystem lib is causing headeaches. If you > and/or Jens (did previous ports to HP) could help me out ... ? > > Once these tools compile, I'll provide fresh status pages every friday like I > do for IBM. That would be excellent - however can you not install a copy of gcc in order to get started? Once the regression tests are being run and results are regularly reported, one would hope that authors will gradually port their libraries to HP. Otherwise you're going to have to liase with the author of whichever lib is causing the problems, I worry that in the absence of regression test feedback, changes to library A will break the regression test helpers on HP before you've fixed the problems on library B :-( Remember also that the regression test programs are regularly tested with gcc, so at least using that you know that you have a solid foundation from which to start your tests... John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
On Wednesday 08 January 2003 17:16, Rene Rivera wrote: > [2003-01-08] Beman Dawes wrote: > >At 07:58 AM 1/8/2003, John Maddock wrote: > > >This is another call for volunteers to come forward to help run the > > > boost regression tests on more platforms, particularly needed are the > > > >commercial > > > > >Unix variants (Solaris, HP, SGI Irix etc), but also Free|Net|OpenBSD and > > >MacOS X. I'm working on the port to HPUX (recently I've send a few msg's out on this) but have trouble compiling the regression-reporting tools. Already patched a few things in MPL but now the filesystem lib is causing headeaches. If you and/or Jens (did previous ports to HP) could help me out ... ? Once these tools compile, I'll provide fresh status pages every friday like I do for IBM. toon ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
RE: [boost] Call for regression test volunteers
I don't know what the restrictions are but it might be worth looking at http://testdrive.hp.com which claims to offer alpha, itanium, PA-RISC, StrongARM and x86 systems running BSD, HP-UX, Linux, OpenVMS and Tru64: "These systems are provided as a convenience for developers and systems integrators worldwide who would like to test their software applications on x86, PA-RISC, Alpha, Itanium, or StrongARM systems but don't currently have easy or convenient access to such systems." I'd try it myself if I could get past the firewall at work or if my firewall at home hadn't caught on fire yesterday (yes really)... > -Original Message- > From: John Maddock [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 8 January 2003 10:58 PM > To: boost > Subject: [boost] Call for regression test volunteers > > This is another call for volunteers to come forward to help run the boost > regression tests on more platforms, particularly needed are the commercial > Unix variants (Solaris, HP, SGI Irix etc), but also Free|Net|OpenBSD and > MacOS X. > > To help kick things off, I've attached a short shell script that will run > the tests and generate the necessary html files given a recent version of > gcc installed on the system. > > Regards, > > John Maddock > http://ourworld.compuserve.com/homepages/john_maddock/index.htm ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
[2003-01-08] Beman Dawes wrote: >At 07:58 AM 1/8/2003, John Maddock wrote: > > >This is another call for volunteers to come forward to help run the boost > >regression tests on more platforms, particularly needed are the >commercial > >Unix variants (Solaris, HP, SGI Irix etc), but also Free|Net|OpenBSD and > >MacOS X. > > > >To help kick things off, I've attached a short shell script that will run > >the tests and generate the necessary html files given a recent version of > >gcc installed on the system. > >Good! This may be useful to some of the compiler suppliers, too. > >Would you be willing to add it to tools/regression? > >Just yesterday I committed a simple tools/regression/index.htm file. A >mention with link to the script could go there, and perhaps a bit of >documentation in more/regression.html. At the least, there should be a link >in more/regression.html. > >In looking at the script, perhaps it could be made a bit clearer what needs >to be changed to tailor it to a particular system. Or perhaps that could be >done in the docs. Anyhow, this should be a helpful addition. John would you mind if I "improve" on the script. I'd like to run it on my OpenBSD server to help out. But I would have to add fetching of Boost from CVS as a step. -- I could document it more as I do this ;-) -- grafik - Don't Assume Anything -- [EMAIL PROTECTED] - [EMAIL PROTECTED] -- 102708583@icq ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Call for regression test volunteers
At 07:58 AM 1/8/2003, John Maddock wrote: >This is another call for volunteers to come forward to help run the boost >regression tests on more platforms, particularly needed are the commercial >Unix variants (Solaris, HP, SGI Irix etc), but also Free|Net|OpenBSD and >MacOS X. > >To help kick things off, I've attached a short shell script that will run >the tests and generate the necessary html files given a recent version of >gcc installed on the system. Good! This may be useful to some of the compiler suppliers, too. Would you be willing to add it to tools/regression? Just yesterday I committed a simple tools/regression/index.htm file. A mention with link to the script could go there, and perhaps a bit of documentation in more/regression.html. At the least, there should be a link in more/regression.html. In looking at the script, perhaps it could be made a bit clearer what needs to be changed to tailor it to a particular system. Or perhaps that could be done in the docs. Anyhow, this should be a helpful addition. Thanks, --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
