Bug#327509: [Pkg-octave-devel] Bug#327509: octave2.1-headers: mkoctfile generates broken binaries ("undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE")

[John W. Eaton]

On 10-Sep-2005, Graeme Smecher wrote:

| Package: octave2.1-headers
| Version: 2.1.71-2
| Severity: important
| 
| mkoctfile no longer produces working .oct files. I've tried compiling
| the hello.cc example:
| 
|     mkoctfile hello.cc
| 
| The mkoctfile command appears to succed. Then:
| 
|     $ octave -q
|     octave:1> hello
|     error: /home/gsmecher/click/halfband/hello.oct: undefined symbol:
|     _ZNSs4_Rep20_S_empty_rep_storageE
|     octave:1>

Running

  echo _ZNSs4_Rep20_S_empty_rep_storageE | c++filt

shows

  std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_S_empty_rep_storage

so I suspect a compiler issue or packaging problem, not a bug in
Octave itself.

What version of g++ was used to build your copy of Octave?  You can
get this information by typing octave_config_info ("CXX_VERSION") at
the octave prompt.

What version of g++ is currently being used on your system by
mkoctfile?

Assuming the versions are not the same, then do you avoid the problem
if you force mkoctfile to use the same compiler version as was used to
compile Octave?

jwe