[C++-sig] boost python - python uuid mismatch

Michael Wieher michael.wieher at gmail.com
Fri Mar 7 16:28:40 CET 2008


It is something I would try.  If 4.0.2 is required for your app, why not
make the compiled bytecode uniform, at least in that respect.

I'm not saying it'll work =) But I'd give it a shot.


2008/3/7, ZiZi Zhao <zzhao at laika.com>:
>
> the Python 2.5.1 was compiled using gcc 3.4.6; and boost.python 1.34.1 gcc
> 4.0.2, which may be 'different enough'.
>
> should I try to recompile python 2.5.1 and boost.python 1.34.1 both with
> gcc 4.0.2?
>
> f.y.i. gcc 4.0.2 is the required compiler for my application.
>
> THANKS,
> ZIZI
> LAIKA
>
>
> ----- Original Message -----
> From: "Michael Wieher" <michael.wieher at gmail.com>
> To: "Development of Python/C++ integration" <c++-sig at python.org>
> Sent: 2008年3月7日 星期五 上午06时19分41秒 (GMT-0800) America/Los_Angeles
> Subject: Re: [C++-sig] boost python - python uuid mismatch
>
> (this might be incorrect, please correct me if I'm wrong, but my
> understanding is...)
> Basically the compiled library, boost.python, in this instance, must be
> compiled by the same/similar-enough compiler.  That is, you need to use the
> same compiler to compile the python installation you're using and the
> library you're importing.  My experience has been that this is not an
> absolute requirement, (two similar-enough compilers work) but if they're
> different enough, there will be a problem.  The version of boost itself is,
> I believe, irrelevant.
>
> 2008/3/7, ZiZi Zhao <zzhao at laika.com>:
> >
> >
> > Hello,
> > I have compiled boost python with python 2.5.1 and had a script written
> > in the same packages, i.e., python 2.5.1 and extended c++
> > class/functions of boost.python.
> >
> > As long as I import some python module that contains 'import uuid', I
> > got
> > "Fatal Python error: version mis-match".
> >
> > Is there anyway to fix this?
> >
> > Thanks,
> >
> > ZIZI
> > LAIKA
> >
> >
> >
> >
> > _____________________________________________________________________
> > The information contained in this message and its attachments is
> > confidential and proprietary to LAIKA, Inc.  By opening this email
> > or any of its attachments, you agree to keep all such information
> > confidential and not to use, distribute, disclose or copy any part
> > of such information without the prior written consent of LAIKA,
> > Inc.  If you are not the intended recipient of this message, any use,
> > distribution, disclosure or copying of such information is prohibited.
> > If received in error, please contact the sender.
> >
> > _______________________________________________
> > C++-sig mailing list
> > C++-sig at python.org
> > http://mail.python.org/mailman/listinfo/c++-sig
> >
>
>
> _____________________________________________________________________
> The information contained in this message and its attachments is
> confidential and proprietary to LAIKA, Inc. By opening this email
> or any of its attachments, you agree to keep all such information
> confidential and not to use, distribute, disclose or copy any part
> of such information without the prior written consent of LAIKA,
> Inc. If you are not the intended recipient of this message, any use,
> distribution, disclosure or copying of such information is prohibited.
> If received in error, please contact the sender.
>
>
> _______________________________________________
> C++-sig mailing list
> C++-sig at python.org
> http://mail.python.org/mailman/listinfo/c++-sig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20080307/fee644c5/attachment.htm>


More information about the Cplusplus-sig mailing list