[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#163422: g++-3.2 not compiled for Common C++ ABI!



On Sat, Oct 05, 2002 at 03:04:54PM -0400, Daniel Jacobowitz wrote:
> On Sat, Oct 05, 2002 at 06:01:43PM +0200, Herbert Valerio Riedel wrote:
> > Package: g++-3.2
> > Version: 1:3.2.1-0pre2
> > Severity: important
> > 
> > see also
> > http://gcc.gnu.org/gcc-3.2/c++-abi.html
> > 
> > "g++-3.2 -v" outputs
> > 
> >  Reading specs from /usr/lib/gcc-lib/alpha-linux/3.2.1/specs
> >  Configured with: /build/buildd/gcc-3.2-3.2.1ds1/src/configure -v
> >  --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr
> >  --mandir=/usr/share/man --infodir=/usr/share/info
> >  --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared
> >  --with-system-zlib --enable-nls --without-included-gettext
> >  --enable-java-gc=boehm --enable-objc-gc alpha-linux
> >  Thread model: posix
> >  gcc version 3.2.1 20020912 (Debian prerelease)
> > 
> > which definitely lacks "--enable-__cxa_atexit"
> > 
> > fyi, other linux distributions (such as redhat-8.0) are using the common
> > ABI convention, if debian does not, we'll suffer interoperability
> > problems with shared C++ libs, and we'll render the whole Common C++ ABI
> > efforts void :-(
> 
> Did we lose a patch somewhere?
> 
> We're now using --disable-__cxa-atexit on NetBSD, and nothing
> elsewhere.  But 3.2 cxa-atexit defaults to off, as far as I can tell...
> The patch at the time said:
> 
> @@ -62,8 +62,11 @@ CONFARGS = -v \
>         --enable-shared \
>         --with-system-zlib \
>         --enable-nls \
> -       --without-included-gettext \
> -       --enable-__cxa_atexit
> +       --without-included-gettext
> +
> +ifneq ($(with_cxa_atexit),yes)
> +  CONFARGS += --disable-__cxa_atexit
> +endif
>  
>  ifeq ($(with_java),yes)
>    CONFARGS += --enable-java-gc=boehm
> 
> And that doesn't look right at all.

The origional patch for NetBSD (as submitted by me) elided the option call
for --enable-__cxa_atexit; this was modified by the maintainers before
application to what you see, with the statement that it was on by default.

Until per-platform patches clear this up, perhaps we need to explicitly
enable or disable it forcibly, rather than letting it default?
-- 
***************************************************************************
Joel Baker                           System Administrator - lightbearer.com
lucifer@lightbearer.com              http://users.lightbearer.com/lucifer/

Attachment: pgpiPTTqgoPpU.pgp
Description: PGP signature


Reply to: