[fdo-internals] automake/autoconf/libtool preferred version?

Traian Stanev traian.stanev at autodesk.com
Sun Feb 11 14:29:32 EST 2007

I remember having to fix this exact thing for my 64 bit build too, but I redeclared the variable len to be the correct type (i.e. not FdoSize, but whatever int Xerces wanted). 

	-----Original Message----- 
	From: fdo-internals-bounces at lists.osgeo.org on behalf of Frank Warmerdam (External) 
	Sent: Sun 2/11/2007 1:26 AM 
	To: FDO Internals Mail List 
	Subject: Re: [fdo-internals] automake/autoconf/libtool preferred version?

	Greg Boone wrote:
	> I am successfully building on Fedora 5 with the following:
	> autoconf (GNU Autoconf) 2.59
	> automake (GNU automake) 1.9.6
	> ltmain.sh (GNU libtool) 1.5.22 (1.2220.2.365 2005/12/18 22:14:06)
	> I have not seen any warnings or errors to speak of.
	I have upgraded to automake 1.9.5 and things are working substantially
	better now.  At the very least this resolved the makefile problem.  Now I'm
	running into this:
	-DPACKAGE_BUGREPORT=\"https://fdocore.osgeo.org\" -DPACKAGE=\"fdo\"
	-I. -I../../Inc -I../Nls -I../Common -I../Geometry
	-I/home/warmerda/fdobase/Thirdparty/apache/xml-xerces/c/src -MMD -MT
	FeaturePropertyReaderImpl.lo -MD -MP -MF .deps/FeaturePropertyReaderImpl.Tpo -c
	Xml/FeaturePropertyReaderImpl.cpp  -fPIC -DPIC -o .libs/FeaturePropertyReaderImpl.o
	Xml/FeaturePropertyReaderImpl.cpp: In member function `virtual FdoBoolean
	FdoXmlFeaturePropertyReaderImpl::XmlEndElement(FdoXmlSaxContext*, const
	FdoString*, const FdoString*, const FdoString*)':
	Xml/FeaturePropertyReaderImpl.cpp:536: error: no matching function for call to
	`xercesc_2_5::Base64::decode(const XMLByte*, FdoSize*)'
	note: candidates are: static XMLByte* xercesc_2_5::Base64::decode(const
	XMLByte*, unsigned int*, xercesc_2_5::MemoryManager*)
	note:                 static XMLCh* xercesc_2_5::Base64::decode(const XMLCh*,
	unsigned int*, xercesc_2_5::MemoryManager*)
	This patch seems to get things building (cast the FdoSize * "&len"
	to be an unsigned int *), but I suspect that this isn't legitimate
	if FdoSize is actually 64bits in size on 64bit machines.  Is that
	the case?
	warmerda at amd64$ svn diff Fdo/Xml/FeaturePropertyReaderImpl.cpp
	Index: Fdo/Xml/FeaturePropertyReaderImpl.cpp
	--- Fdo/Xml/FeaturePropertyReaderImpl.cpp       (revision 2498)
	+++ Fdo/Xml/FeaturePropertyReaderImpl.cpp       (working copy)
	@@ -533,7 +533,8 @@
	      case ParsingState_base64Binary:
	              FdoSize len;
	-            XMLByte* decoded = XERCES_CPP_NAMESPACE::Base64::decode((const
	XMLByte*)(const char*)m_dataProperty, &len);
	+            XMLByte* decoded = XERCES_CPP_NAMESPACE::Base64::decode((const
	XMLByte*)(const char*)m_dataProperty,
	+                                                                    (unsigned
	int *) &len);
	              if (decoded != NULL) {
	decoded, len);
	I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
	light and sound - activate the windows | http://pobox.com/~warmerdam
	and watch the world go round - Rush    | President OSGeo, http://osgeo.org
	fdo-internals mailing list
	fdo-internals at lists.osgeo.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20070211/4067a1e6/attachment.html

More information about the fdo-internals mailing list