Hello developers, We're facing problems regarding a compilation of Xalan-c 1.10 with Xerces 2.7 with the compiler gcc 4.3.2:
Normally we compile with options "-Werror -Wall". If we compile with gcc 3 there are no problems related, but when compiling with gcc 4. ----- The compiler reported the following errors: --------- cc1plus: warnings being treated as errors In file included from /user/Xalan/include/xalanc/PlatformSupport/DOMS tringHelper.hpp:44, from /user/Xalan/include/xalanc/PlatformSupport/Xala nDOMStringPool.hpp:27, from /user/Xalan/include/xalanc/DOMSupport/DOMSuppor tDefault.hpp:26, from /user/Xalan/include/xalanc/XercesParserLiaison/ XercesDOMSupport.hpp:27, from src/otf/backend/backendContext/ResourcesImpl.cpp:19: /user/Xalan/include/xalanc/XalanDOM/XalanDOMStr ing.hpp: In member function 'xalanc_1_10::XalanDOMString& xalanc_1_10::XalanDOMString::substr(xalanc_1_10::XalanDOMString&, unsigned int, unsigned int) const': /user/Xalan/include/xalanc/XalanDOM/XalanDOMStr ing.hpp:574: error: suggest parentheses around && within || /user/Xalan/include/xalanc/Include/XalanVector. hpp: In member function 'void xalanc_1_10::XalanVector<Type, ConstructionTraits>::invariants() const [with Type = short unsigned int, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<short unsigned int>]': /user/Xalan/include/xalanc/Include/XalanVector. hpp:235: instantiated from 'xalanc_1_10::XalanVector<Type, ConstructionTraits>::~XalanVector() [with Type = short unsigned int, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<short unsigned int>]' /user/Xalan/include/xalanc/XalanDOM/XalanDOMStr ing.hpp:95: instantiated from here /user/Xalan/include/xalanc/Include/XalanVector. hpp:913: error: suggest parentheses around && within || /user/Xalan/include/xalanc/Include/XalanVector. hpp: In member function 'void xalanc_1_10::XalanVector<Type, ConstructionTraits>::invariants() const [with Type = char, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<char>]': /user/Xalan/include/xalanc/Include/XalanVector. hpp:128: instantiated from 'xalanc_1_10::XalanVector<Type, ConstructionTraits>::XalanVector(xercesc_2_6::MemoryManager&, size_t) [with Type = char, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<char>]' /user/Xalan/include/xalanc/XalanDOM/XalanDOMStr ing.hpp:1043: instantiated from here /user/Xalan/include/xalanc/Include/XalanVector. hpp:913: error: suggest parentheses around && within || /user/Xalan/include/xalanc/Include/XalanVector. hpp: In member function 'void xalanc_1_10::XalanVector<Type, ConstructionTraits>::invariants() const [with Type = const xalanc_1_10::XalanDOMString*, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<const xalanc_1_10::XalanDOMString*>]': /user/Xalan/include/xalanc/Include/XalanVector. hpp:235: instantiated from 'xalanc_1_10::XalanVector<Type, ConstructionTraits>::~XalanVector() [with Type = const xalanc_1_10::XalanDOMString*, ConstructionTraits = xalanc_1_10::MemoryManagedConstructionTraits<const xalanc_1_10::XalanDOMString*>]' /user/Xalan/include/xalanc/Include/XalanMemMgrA utoPtr.hpp:268: instantiated from 'void xalanc_1_10::XalanMemMgrAutoPtrArray<Type>::MemMgrAutoPtrArrayData::deal locate() [with Type = xalanc_1_10::XalanVector<const xalanc_1_10::XalanDOMString*, xalanc_1_10::MemoryManagedConstructionTraits<const xalanc_1_10::XalanDOMString*> >]' /user/Xalan/include/xalanc/Include/XalanMemMgrA utoPtr.hpp:345: instantiated from 'xalanc_1_10::XalanMemMgrAutoPtrArray<Type>::~XalanMemMgrAutoPtrArray() [with Type = xalanc_1_10::XalanVector<const xalanc_1_10::XalanDOMString*, xalanc_1_10::MemoryManagedConstructionTraits<const xalanc_1_10::XalanDOMString*> >]' /user/Xalan/include/xalanc/PlatformSupport/Xala nDOMStringHashTable.hpp:65: instantiated from here /user/Xalan/include/xalanc/Include/XalanVector. hpp:913: error: suggest parentheses around && within || We are wondering if it's expected to release changes to adapt Xalan-c1.10 to gcc 4. So far we have modified the sources simply with: assert((m_data == 0 && m_allocation == 0) || (m_data != 0 && m_allocation != 0)); Instead of the original: assert(m_data == 0 && m_allocation == 0 || m_data != 0 && m_allocation != 0); Is the Xalan project expecting to release a version adapted to gcc 4? Is there an aditional source of information since Xalan-c 1.10 release in 2007? There haven't been any releases in 3 years, and I'm surprised that I haven't found any update for gcc 4 Thanks for your responses. Best regards, Christina.
