[Xapian-tickets] [Xapian] #403: Could not find a match for std::vector<unsigned>::assign since 1.0.12

Xapian nobody at xapian.org
Mon Nov 16 09:37:24 GMT 2009


#403: Could not find a match for std::vector<unsigned>::assign since 1.0.12
------------------------+---------------------------------------------------
 Reporter:  dmichelsen  |        Owner:  olly  
     Type:  defect      |       Status:  closed
 Priority:  normal      |    Milestone:  1.0.17
Component:  Other       |      Version:  1.0.12
 Severity:  blocker     |   Resolution:  fixed 
 Keywords:              |    Blockedby:        
 Platform:  Solaris     |     Blocking:        
------------------------+---------------------------------------------------
Changes (by olly):

  * status:  assigned => closed
  * resolution:  => fixed
  * milestone:  1.1.3 => 1.0.17


Comment:

 OK, the 1.0 branch builds fine for me on build8s with
 {{{CXX=/opt/studio/SOS11/SUNWspro/bin/CC}}} which I assume is version 11
 from the pathname, though CC -V reports "CC: Sun C++ 5.8 Patch 121017-20
 2009/04/22".

 {{{CXX=/opt/csw/gcc4/bin/g++}}} on build8s fails at configure time because
 built binaries don't run due to library search path issues (which sounds
 like an installation issue to me):

 {{{
 -bash-4.0$ cat hellow.cc
 #include <iostream>
 using namespace std;
 int main() {
     cout << "Hello World" << endl;
 }
 -bash-4.0$ /opt/csw/gcc4/bin/g++ -O2 -o hellow hellow.cc
 -bash-4.0$ ./hellow
 ld.so.1: hellow: fatal: libstdc++.so.6: open failed: No such file or
 directory
 Killed
 -bash-4.0$
 }}}

 Anyway, I think this bug has become much too confused - we have several
 different and unrelated issues with different compilers in here, many of
 which are fixed, and the only commonality is really that they happen on
 Solaris.  The problem actually described in the title and description is
 now fixed, and I've also fixed a number of other issues on Solaris, so I'm
 going to close this ticket.

 I'm working towards being able to run scripted builds on the opencsw farm,
 so I should pick up any other issues eventually, but meanwhile if you run
 into further problems, please do open tickets for them, but please keep
 them as separate tickets unless the errors clearly have a common cause, so
 that we can sanely track them separately.

-- 
Ticket URL: <http://trac.xapian.org/ticket/403#comment:14>
Xapian <http://xapian.org/>
Xapian



More information about the Xapian-tickets mailing list