On 14 May 2012 at 16:22, Jonas Wielicki wrote:
> > Debian doesn't necessarily install by default
> > multiple versions of compilers, rather they're in the repos available
> > as package dependencies. Surely Fedora is the same?
> Nope, I was talking about the repositories.
Well, well. Didn't thi
>>> Clang doesn't compile boost python 1.49 at all. Sadly.
> Sure, you're right. Sorry, it was my fault in reading clang's error
> messages. It chockes on the c++ stl bits, not on boost, but they're
> included from boost, so the first thing I read was “boost”.
> Well, I cannot tell if it would chok
On 05/14/2012 04:05 PM, Niall Douglas wrote:
> Debian doesn't necessarily install by default
> multiple versions of compilers, rather they're in the repos available
> as package dependencies. Surely Fedora is the same?
Nope, I was talking about the repositories.
> Ah, my build system has been sc
On 14 May 2012 at 15:11, Jonas Wielicki wrote:
> On 05/14/2012 01:33 PM, Niall Douglas wrote:
> > Most distros bundle multiple versions of gcc due to this exact
> > problem with frequent bugs. Debian, at least, usually has the
> > previous version and for many years also had the latest from the
On 05/14/2012 01:33 PM, Niall Douglas wrote:
> Most distros bundle multiple versions of gcc due to this exact
> problem with frequent bugs. Debian, at least, usually has the
> previous version and for many years also had the latest from the 3.x
> and indeed 2.x series.
Well, Fedora doesn't. They
On 14 May 2012 at 12:53, Jonas Wielicki wrote:
> > Generally speaking GCC bugs fix themselves over
> > time, so you can revert temporarily to an older GCC. Bugs in GCC are
> > common enough that if my code fails, I first think it's GCC's fault
> > :)
> Hm. GCC updates are rather rare though I th
Hello, I using bjam to compile my C++ program with Boost.Python But I have a
link error : error LNK2019: unresolved external symbol
"__declspec(dllimport) so I try to add my library in the Jamroot file :
project
: requirements /boost/python//boost_python
D:/localExt_win32_cl10-0Ex
On 14/05/12 12:37, Niall Douglas wrote:
> I would be almost certain that your bug stems from changes to GCC,
> not changes to BPL.
By now, this is also my suspect. Mainly, because it should be just one
function call between the value being correct and being wrong, while it
is only passed as a by-
On 14 May 2012 at 9:48, Jonas Wielicki wrote:
> I recently upgraded to boost::python 1.48 and g++ 4.7 (fedora 17). This
> broke a project of mine as it crashes when passing an object with
> virtual inheritance from python back to C++ (e.g. during a method call).
> A minimal test case is attached.
On 13 May 2012 at 14:31, Stefan Seefeld wrote:
> On 05/13/2012 05:18 AM, Michele De Stefano wrote:
> > I've read a recent post by Jim Bosch saying that the original
> > developers of Boost Python are not going to upgrade it for supporting
> > C++11 standard libraries.
>
> Can you elaborate a litt
On 13 May 2012 at 21:28, Michele De Stefano wrote:
> I read that post from Jim Bosch and I thought he knew something more about
> Boost Python development.
What Jim didn't mention is how BPL v2 (the current version) was first
written. Basically, Berkeley paid Dave Abrahams a chunk of money to
(
Moin folks,
I recently upgraded to boost::python 1.48 and g++ 4.7 (fedora 17). This
broke a project of mine as it crashes when passing an object with
virtual inheritance from python back to C++ (e.g. during a method call).
A minimal test case is attached.
After nearly an hour of debugging in a si
Moin folks,
I recently upgraded to boost::python 1.48 and g++ 4.7 (fedora 17). This
broke a project of mine as it crashes when passing an object with
virtual inheritance from python back to C++ (e.g. during a method call).
A minimal test case is attached.
After nearly an hour of debugging in a si
13 matches
Mail list logo
