[C++-sig] more boost v1 problems

[David Abrahams]

All I can tell you offhand is:

0. 2.96 is not an official GCC release version
1. it is working for me here with GCC 3.2 on Debian.
2. This crash might well be due to a problem with C++ exception-handling.

Hmm, how did you configure your GCCs? I have it on good authority that for
GCCs prior to 3.1 need to be configured with

    --prefix=... --enable-version-specific-runtime-libs

if you have an existing GCC installation. For versions 3.1 and greater,

    --prefix=...

is sufficient.

HTH,
Dave

-----------------------------------------------------------
           David Abrahams * Boost Consulting
dave at boost-consulting.com * http://www.boost-consulting.com


----- Original Message -----
From: <cseymour at interchange.ubc.ca>
To: "David Abrahams" <dave at boost-consulting.com>
Cc: <c++-sig at python.org>
Sent: Wednesday, August 21, 2002 8:53 PM
Subject: Re: Re: [C++-sig] more boost v1 problems


> 1) boost 1.28.0
> 2) no. the glibc was just changed by changing the RPM on the dead
computer. only the dead computer was affected. Python was built with gcc
2.96 and 3.0.4 on a different computer using glibc 2.2.4.
> 3) n/a. the computer i'm working on now has always had glibc 2.2.4.
>
> i don't think its a glibc thing, but thats the only variable i can think
of.
>
> -----Original Message-----
>
> > Date: Wed Aug 21 17:25:30 PDT 2002
> > From: David Abrahams <dave at boost-consulting.com>
> > Subject: Re: [C++-sig] more boost v1 problems
> > To: c++-sig at python.org
> >
> > 1. Are you using the current boost CVS state, or something earlier?
> > 2. Have you rebuilt everything from scratch since changing your glibc?
> > 3. Have you rebuilt/reinstalled your GCC since changing your glibc?
> >
> > I have to admit, glibc compatibility issues are black magic to me, but
#3
> > sounds like the sort of thing that could be an issue.
> >
> > -Dave
> >
> > -----------------------------------------------------------
> >            David Abrahams * Boost Consulting
> > dave at boost-consulting.com * http://www.boost-consulting.com
> >
> > From: <cseymour at interchange.ubc.ca>
> >
> >
> > > Hello again,
> > >
> > > sorry for posting about this again but i can't figure it out...
> > > I had boost working yesterday, but today (the computer it was working
on
> > is fried) it refuses to work.
> > >
> > > I'm using the linux gcc makefile. I've tried g++ 2.96 (which it
worked
> > with before) and python 2.2.1 compiled with g++ 2.96, and also g++
3.0.4
> > and python 2.2.1 compiled with g++ 3.0.4 (which the boost python
webpage
> > says should work). in both cases, when running comprehensive.py it
fails
> > like so:
> > >
> > > 1
> > > 2
> > > 3
> > > Running comprehensive.__doc__
> > > Trying:
> > > try:
> > >     ext = Foo()
> > > except TypeError, err:
> > >     assert re.match(r'function .* exactly 1 argument;? \(?0
given\)?',
> > >                     str(err))
> > > else:
> > >     print 'no exception'
> > > Expecting: nothing
> > > Aborted
> > >
> > > and i assume this is because of the ABI / exception handling
problems. my
> > extension modules seem to work, except when they try to throw
exceptions.
> > >
> > > the only difference i can think of between computers is that the
computer
> > I was working on before had glibc version 2.2.5 installed, while the
rest
> > have 2.2.4 (it was in changing glibc back that the computer died)
> > >
> > > does anyone have any ideas on what i could do? again, sorry for sort
of
> > re-posting but i've worked at this and can't figure it out
> >
> >
> >
> > _______________________________________________
> > C++-sig mailing list
> > C++-sig at python.org
> > http://mail.python.org/mailman/listinfo/c++-sig
>
>