[jira] Created: (XERCESC-1907) PDB file name for static 64-bit debug builds in VC8 and VC9 project files are not library specific
PDB file name for static 64-bit debug builds in VC8 and VC9 project files are not library specific -- Key: XERCESC-1907 URL: https://issues.apache.org/jira/browse/XERCESC-1907 Project: Xerces-C++ Issue Type: Bug Components: Build Affects Versions: 3.1.0 Environment: Windows Reporter: Boris Kolpackov Priority: Minor The PDB file for static 64-bit debug builds in VC8 and VC9 project files are still names xerceslib_vc80.pdb. We have fixed this for 32-bit builds but not for 64-bit, for some reason. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] Closed: (XERCESC-1904) Cannot build shared library from xerces-c 3.0.1 on AIX6.1 with xlC V10.1
[ https://issues.apache.org/jira/browse/XERCESC-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Kolpackov closed XERCESC-1904. Resolution: Fixed Fix Version/s: 3.1.0 Assuming fixed in the just-released 3.1.0. Cannot build shared library from xerces-c 3.0.1 on AIX6.1 with xlC V10.1 Key: XERCESC-1904 URL: https://issues.apache.org/jira/browse/XERCESC-1904 Project: Xerces-C++ Issue Type: Bug Components: Build Affects Versions: 3.0.1 Environment: OS : AIX 6.1 TL3 SP1 Compiler: IBM XL C/C++ Enterprise Edition for AIX, V10.1 Reporter: Gauthier Helin Priority: Blocker Fix For: 3.1.0 Attachments: config.log, config.log_3.1.0 Hello, I cannot build the xerces 3.0.1 shared library on AIX 6.1 with xlC 10.1. It always produce the static library even if I specify --enable-shared=yes. I tried may different ./configure and gmake options without any success. here is some output of the ./configure which shows that it thinks that the linker does not support shared libs : checking if xlc_r supports -c -o file.o... yes checking whether the xlc_r linker (/usr/bin/ld) supports shared libraries... no checking dynamic linker characteristics... no checking how to hardcode library paths into programs... unsupported checking whether stripping libraries is possible... no checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking whether the xlC_r linker (/usr/bin/ld) supports shared libraries... no checking for xlC_r option to produce PIC... checking if xlC_r static flag works... yes checking if xlC_r supports -c -o file.o... yes checking whether the xlC_r linker (/usr/bin/ld) supports shared libraries... no checking dynamic linker characteristics... no (cached) (cached) checking how to hardcode library paths into programs... unsupported appending configuration tag F77 to libtool checking whether xlc_r and cc understand -c and -o together... yes the command line used was : ./configure --prefix=$PREFIX CXX=xlC_r CC=xlc_r --enable-shared=yes gmake libxerces_c_la_LDFLAGS=-qmkshrobj This was working fine on AIX 5.3 with xlC 7 Thanks a lot for any help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xml Vulnerability issue with C Xerces
Atul Parti atulpa...@gmail.com writes: is there any patch or maybe any latest version which has handle this issue and can be used directly. If you refer to the CVE-2009-1885 vulnerability, then it has been fixed in the just-released Xerces-C++ 3.1.0. Boris -- Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde Command line interface to C++ compiler http://codesynthesis.com/projects/cli - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
LNK2019 error from newbie
hi, i didn't find the details from http://xerces.apache.org/xerces-c/install-3.html#Windows guess someone might asked it before, but don't know where to search. basically i'm using VC 2005 (VC 8.0) to try the 1st example, got this, Error2error LNK2019: unresolved external symbol __declspec(dllimport) public: static void __cdecl xercesc_3_0::XMLPlatformUtils::Terminate(void) (__imp_?termin...@xmlplatformutils@xercesc_3_0@@SAXXZ) referenced in function __catch$_wmain$0xml1.obj my install is in C:\opt\xercesc i have C:\opt\xercesc\bin in the path, i have the additional include/lib directories in the VC property page. C:\opt\xercesc\include C:\opt\xercesc\lib What else could be missing ? thanks ! _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/201469226/direct/01/
[jira] Created: (XERCESC-1908) Xerces-c SAX application crashed on Solaris 10 x64
Xerces-c SAX application crashed on Solaris 10 x64 -- Key: XERCESC-1908 URL: https://issues.apache.org/jira/browse/XERCESC-1908 Project: Xerces-C++ Issue Type: Bug Components: SAX/SAX2 Affects Versions: 2.7.0, 2.8.0, 3.0.0, 3.0.1 Environment: $uname -a SunOS xsol-qa1 5.10 Generic_137138-09 i86pc i386 i86pc $CC -V CC: Sun C++ 5.7 2005/01/07 Reporter: Bill Fu This issue just happens on Solaris 10 x64. There is no problem on other platforms, such as Solaris 10 x86 (32-bit), AIX (both 32 and 64), HP-UX (both PA-RISC and IA64), Linux x86 etc. I wrote a xerces-c sax application on Solaris 10 x64. The class MXmlHandler was the xml handler what was inherited from DefaultHandeler. The following is the compiler and linker flags. Compiler flags: -mt -xarch=amd64 -g -I/usr/app/xercesc/2.8/include Linker flags: -mt -xarch=amd64 -L/usr/app/xercesc/2.8/lib -lxerces-c At the begining of the method void startElement( const XMLCh* consturi, const XMLCh* constlocalname, const XMLCh* constqname, const Attributes attributes); the value of the parameter qname was wrong. For example the qname should be a string like schemaName, but it was a recognised string. This is the behavior in RELEASE libraries. In the DEBUG mode, the application crashed in xerces-c libraries. The following is traceback. =[1] xercesc_2_8::XMLAttr::getValue(this = 0x18), line 486 in XMLAttr.hpp [2] xercesc_2_8::VecAttrListImpl::getValue(this = 0x4cc3e8, index = 1U), line 86 in VecAttrListImpl.cpp [3] 0xfd7ffeab6546(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7ffeab6545 [4] xercesc_2_8::SAXParser::startElement(this = 0x4cc3a8, elemDecl = CLASS, elemURLId = 1U, elemPrefix = 0xfd7ffe1bb3b0, attrList = CLASS, attrCount = 2U, isEmpty = false, isRoot = true), line 971 in SAXParser.cpp [5] xercesc_2_8::IGXMLScanner::scanStartTag(this = 0x4cd6b8, gotData = true), line 2101 in IGXMLScanner.cpp [6] xercesc_2_8::IGXMLScanner::scanContent(this = 0x4cd6b8), line 899 in IGXMLScanner.cpp [7] xercesc_2_8::IGXMLScanner::scanDocument(this = 0x4cd6b8, src = CLASS), line 215 in IGXMLScanner.cpp [8] xercesc_2_8::XMLScanner::scanDocument(this = 0x4cd6b8, systemId = 0x4d4530), line 460 in XMLScanner.cpp [9] xercesc_2_8::XMLScanner::scanDocument(this = 0x4cd6b8, systemId = 0x4c7f68 ../dats/adr3xml.dat), line 468 in XMLScanner.cpp [10] xercesc_2_8::SAXParser::parse(this = 0x4cc3a8, systemId = 0x4c7f68 ../dats/adr3xml.dat), line 587 in SAXParser.cpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
