I found an example of a person experiencing the same compile error using xlc on
AIX for a different project. They indicated what their fix was, but I am not
sure how to apply the same fix to the qpid source (or if it will work). Am I
off base here or can the same fix be applied to qpid and if so, how should the
qpid source be modified to accomplish that goal?
[ 12%] Building CXX object
source/geometry/CMakeFiles/G4geometry.dir/navigation/src/G4Navigator.cc.o
"/usr/vacpp/include/vector.t", line 72.54: 1540-0215 (S) The wrong number of
arguments have been specified for
"G4EnhancedVecAllocator<G4NavigationLevel>::allocate(size_t)".
"/usr/vacpp/include/vector.t", line 60.6: 1540-0700 (I) The previous message
was produced while processing
"std::vector<G4NavigationLevel,G4EnhancedVecAllocator<G4NavigationLevel>
>::insert(iterator, size_type, const G4NavigationLevel &)".
"/usr/vacpp/include/vector", line 198.25: 1540-0700 (I) The previous message
was produced while processing
"std::vector<G4NavigationLevel,G4EnhancedVecAllocator<G4NavigationLevel>
>::resize(size_type, G4NavigationLevel)".
"/home01/r668btg/geant4.9.6.b01/source/geometry/volumes/include/G4NavigationHistory.icc",
line 193.6: 1540-0700 (I) The previous message was produced while processing
"G4NavigationHistory::NewLevel(G4VPhysicalVolume *, EVolume, G4int)".
=========================================================
My fix:
=========================================================
#if defined(WIN32) || defined(__IBMCPP__)
std::vector<G4NavigationLevel> fNavHistory;
#else
std::vector<G4NavigationLevel,G4EnhancedVecAllocator<G4NavigationLevel> >
fNavHistory;
// The geometrical tree; uses specialized allocator to optimize
// memory handling and reduce possible fragmentation
#endif
Thanks,
Chris Whelan
