From: David Abrahams (dave_at_[hidden])
Date: 2006-09-29 05:21:04
Markus SchÃ¶pflin <markus.schoepflin_at_[hidden]> writes:
> Interestingly, all of the failing tests either use the jam rule run or
> py-run. All tests using the rule bpl-test are working fine.
I think I fixed that case.
> And the toolset gcc-4.1.1_sunos_i86pc shows failures for the same tests,
> although the exact error is different.
I think that's a different, but related, issue. At first I thought
it had to do with the fact that python.jam is using
<find-shared-library> when no libpythonXX on unix is ever shared
[Volodya, why did you specify find-shared-library there?], but
it seems gcc doesn't distinguish between find-shared-library and
find-static-library anyway, so that can't be the explanation. I've
asked Caleb to look at that failure.
> What is the intended difference between these two test rules?
One runs python, which dynamically loads extension modules. The other
runs a user program that embeds python.
> Why isn't there just one test rule?
They're totally different.
> And does anyone know why it works in one case, but not the other?
Python is already linked with libz on those platforms where it's
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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