BOOST program options and libstdc++5



I got the following problem with libboost-program-options1.32.0 on my
system:

/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../lib/libboost_program_options.so, may conflict with libstdc++.so.6

And indeed, it segfaults when trying to run the program (gdb):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212495648 (LWP 22704)]
0xb7e72540 in std::string::compare () from /usr/lib/libstdc++.so.6

Is this a bug of libboost-program-options1.32.0, that should be rebuilt
against libstdc++6, as it seems that GCC 4.0 is the current standard
compiler?

Doubtfully,
Nowhere man
--
nowhere.man@xxxxxxxxxxxxxxxx
OpenPGP 0xD9D50D8A

Attachment:signature.asc
Description: Digital signature



Relevant Pages

  • scsi_id segfault with udev-009
    ... Program received signal SIGSEGV, Segmentation fault. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • RE: stack overflow help ..
    ... Do an "info frame" in gdb. ... (no debugging symbols found)...(no debugging symbols ... Program received signal SIGSEGV, Segmentation fault. ...
    (Security-Basics)
  • awk(1) segfaults when building kernel modules
    ... `make -s buildkernel' seems to contain lots of segfaults after recent ... Program received signal SIGSEGV, Segmentation fault. ...
    (freebsd-current)
  • Opera SIGSEGV
    ... Opera newsreader stack for those who care: ... Program received signal SIGSEGV, Segmentation fault. ...
    (comp.os.linux.misc)
  • Re: ncurses segfaults in Debian woody?
    ... > Tracing with gdb i get the message: ... > Program received signal SIGSEGV, Segmentation fault. ... > this is the backtrace: ...
    (comp.os.linux.development.apps)