On 10/21/2010 04:48 PM, Jonathan Robie wrote:
> On 10/21/2010 03:33 PM, Robert Schweikert wrote:
>
>> I am attaching the .i file.
>>
>> So if 2.2.3 works for you I guess there might be some instantiation
>> issue. I am building with 4.4.1, or an issue with boost. I am using 1.39
>
> I suspect this may be an autotools configuration issue. If you look at
> configure.ac, it checks to see if
> <xqilla/ast/XQEffectiveBooleanValue.hpp> is available.
That's interesting, I do not see this check. Here is the section of
configure.ac that deals with XQilla:
# If the user doesn't say not to use XML, see if it's available.
if test $use_xml != no; then
# Then see if XQilla is available
tmp_LIBS=$LIBS
AC_CHECK_LIB([xerces-c], [_init], , [use_xml=no])
AC_CHECK_HEADER([xercesc/framework/MemBufInputSource.hpp], , [use_xml=no])
AC_CHECK_HEADER([xqilla/xqilla-simple.hpp], , [use_xml=no])
AC_CHECK_LIB([xqilla], [_init], , [use_xml=no])
# Remove from LIBS, we will link it explicitly in make files.
LIBS=$tmp_LIBS
# If XQilla is not available, yet specifically requested, die.
test $use_xml:$want_xml = no:yes &&
AC_MSG_ERROR([XML Exchange requested, but XQilla or Xerces-C not
available])
# Else XQilla is available - use it to build
test $use_xml = yes &&
AC_DEFINE([HAVE_XML], [1], [Compile-in XML Exchange support.])
fi
AM_CONDITIONAL([HAVE_XML], [test $use_xml = yes])
Did I end up with an incomplete/corrupt tarball?
I am using qpid-cpp-0.6.tar.gz as this appears to be the the latest
released version.
>
>> # Check to see if we need to use legacy calls for effective boolean
>> value
>> xqilla_has_ebv=yes
>> AC_CHECK_HEADER([xqilla/ast/XQEffectiveBooleanValue.hpp], ,
>> [xqilla_has_ebv=no])
>> test $xqilla_has_ebv = yes &&
>> AC_DEFINE([XQ_EFFECTIVE_BOOLEAN_VALUE_HPP], [1], [XQilla version
>> has xqilla/ast/XQEffectiveBooleanValue.hpp.])
>
> Perhaps AC_CHECK_HEADER is not finding the header file?
>
> If you look at XmlExchange.cpp, it checks this define to see whether to
> include the file that defines effective boolean value:
>
>> #ifdef XQ_EFFECTIVE_BOOLEAN_VALUE_HPP
>> #include <xqilla/ast/XQEffectiveBooleanValue.hpp>
>> #endif
This check does not exist in my source.
Now I am confused.
Thanks,
Robert
>
> Later on, it uses the same define to decide whether to use the older
> XQilla API or the newer one:
>
>> #ifdef XQ_EFFECTIVE_BOOLEAN_VALUE_HPP
>> Item::Ptr first_ = result->next(context.get());
>> Item::Ptr second_ = result->next(context.get());
>> return XQEffectiveBooleanValue::get(first_, second_,
>> context.get(), 0);
>> #else
>> return result->getEffectiveBooleanValue(context.get(), 0);
>> #endif
>
> What happens if you set XQ_EFFECTIVE_BOOLEAN_VALUE_HPP by hand?
>
> Jonathan
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
Software Engineer Consultant LINUX
[email protected]
781-464-8147
Novell
Making IT Work As One
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
