devel/boost: new patch for testing update to 1.39

[Alexander Churanov]

Mel,

I do not understand.

Is it correct that you are discussing the issue of Pyste being part of
boost and depending on gccxml port, which has issues of its own?

I do not use Pyste and did not performed any specific testing of it,
but all of boost-python-libs builds and installs, including
dependencies.

Please, describe what do you expect from ports and what do you
observe, what negative outcome the issue has.

Sincerely,
Alexander Churanov,
maintainer of devel/boost-*


2009/7/30 Mel Flynn <mel.flynn+fbsd.ports at mailing.thruhere.net>:
> On Monday 29 June 2009 05:44:20 Alexander Churanov wrote:
>
>> I've made several changes to new set of boost ports. Please, review
>> them and test new set of ports, if possible.
>
> I guess I should've tested these, but I didn't expect it to replace a minor
> CONFLICTS problem that I had locally patched with a few lines, with a major
> not optional dependency on a retired compiler.
>
> Is pyste going to be optional in a new revision or is there any chance gccxml
> can be patched so it builds cleanly with the current GCC?
>
> If the Makefile comment is the only problem, surely it can be addressed?
>
> # GCC-XML has some constructs that GCC 4.2 does not like. Namely,
> # the use of casted-pointer-dereferences as an lvalue to post-increment
> # operations.
>
> Additionally the gccxml port seems pretty much dead. An attempt of revival has
> been done in 2007, but no release has ever been made.
> --
> Mel
>