see also:
http://lists.randombit.net/pipermail/cryptography/2013-April/004193.html
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
On 16.06.2012 17:57, vikas chauhan wrote:
> Is it possible to do what I want ( i.e add separate attributes using the
> single geta()/seta() functions ) or I need to write some kind of wrapper
> functions (each for accessing each a[i]) ?
I guess the simplest way to do that is to template the geta a
On 22.05.2012 19:05, Niall Douglas wrote:
> Do post the bugzilla link here, I'd like to CC into it.
There you go:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53455
I hope they won't murder me for the .gz ;).
--
Jonas
___
Cplusplus-sig mailing list
Cplu
On 22.05.2012 18:07, Gabe Rives-Corbett wrote:
> how would I instruct bjam to use gcc at a specific location and with the
> -std=c++0x flag?
I found that the following works if you replace the existing section of
the project-config.jam file in the boost source tarball:
>>> snip
# Compiler config
On 22.05.2012 16:43, Niall Douglas wrote:
> Precompiled headers on GCC are basically a dump of state just after
> processing the headers. As a result, the file is huge. That might
> help you find out if they're on. I believe bjam defaults them to off.
Well, in that case I'm not using them. They w
On 21.05.2012 17:55, Niall Douglas wrote:
> 1. Does the bug occur in non-optimised as well as optimised builds?
It does.
> 2. Does the bug occur when C++11 is turned off?
It does not.
> 3. What are your -fvisibility settings?
Unchanged to default... Does this help any? Can I find out whats defaul
On 19.05.2012 00:43, Gabe Rives-Corbett wrote:
> Is there any possible workaround to use inheritance with GCC 4.7?
I know of none, sorry. I'd like to use more c++11 features too, but for
now I am forced to stick with 4.6.3. I am working on a bugreport on that
topic though. However, my time is pret
On 19.05.2012 12:01, Jonas Wielicki wrote:
> I am working on a bugreport for the gcc folks right now, and during that
> I came across the release notes for gcc 4.7[1] and found the following.
missed reference, sorry:
[1] http://gcc.gnu.org/gcc-4.7/changes.html#cxx
--
Okay, due to the other thread over there, I came back to this topic even
after I reverted to fedora 16 due to some other issues (they actually
removed ddate. Still cannot believe!)
I am working on a bugreport for the gcc folks right now, and during that
I came across the release notes for gcc 4.7[
On 18.05.2012 19:47, Niall Douglas wrote:
> So it was a bug in GCC after all. Useful to know.
Sorry that I forgot to mention. I was pretty sure it was the GCC after I
tried with two different Boost versions and the very same code was
running fine on gcc 4.6.3 platforms. It is not 100% bulletproof,
On 17/05/12 23:42, Gabe Rives-Corbett wrote:
> I'm getting a seg fault when trying to call a virtual method on a base class
> from python.
I had a similar problem a few days ago. Which g++ version are you using?
I had problems with 4.7.0 (redhat) while 4.6.3 (redhat) was working fine.
--
Jonas
_
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
d
> system does.
Hm. How did you implement that? I mean, does the build chain build its
own gcc if neccessary and install it to a well-defined path in the
user's home directory?
> On 14 May 2012 at 12:53, Jonas Wielicki wrote:
>> Do you recommend to
>> submit a bug report
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-
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
16 matches
Mail list logo
