From: Niklaus Giger (NiklausGiger_at_[hidden])
Date: 2005-03-14 15:38:38
Here is my patch. On Cygwin there were about four tests that failed before and
after applying this patch.
On my Powerbook (GNU/Linux with Debian testing) most Unittests fail before and
after after complaining that they could not find the gcc toolset. I thought
that getting a fresh copy from CVS, building bjam in jam_src, then going to
the v2/test-directory should result in a working environment for tests. Or
did I miss something. python test_all.py gcc didn't help neither. Both gcc
and g++ are installed and have version 3.3.5.
Would it be helpful to setup a small daily cron job which fetches the latest
CVS, rebuilds bjam, runs the test and E-mails me the output, so that I could
forward it after the interesting aspects after a visual inspection to this
list? Is there somewhere such a script? (I cannot guarantee that I would take
a look at the output every day.)
Could please somebody revise this patch and commit if it is okay? Feel free to
suggest more improvements.
-- Niklaus Giger Wieshoschet 6 CH-8753 Mollis --Boundary-00=_OZfNCZ2s65mG6OP Content-Type: application/x-gzip; name="abs_dir.diff.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="abs_dir.diff.gz" [Attachment content not displayed.] --Boundary-00=_OZfNCZ2s65mG6OP Content-Type: application/x-gzip; name="abs_workdir.py.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="abs_workdir.py.gz" [Attachment content not displayed.] --Boundary-00=_OZfNCZ2s65mG6OP--
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk