Re: [Quantlib-dev] Re: The build...

[Dirk E. <ed...@de...>]

  "Luigi" == Luigi Ballabio <bal...@ma...> writes:
  Luigi>  Here is the problem:
  Luigi> 
  >> QuantLib/quantlib_wrap.cpp:31633: cannot allocate an object of type
  >> `QuantLib::Calendar' QuantLib/quantlib_wrap.cpp:31633: since type
  >> `QuantLib::Calendar' has abstract virtual functions
  Luigi>  for some reason gcc displays a few more cascading errors/warnings
  Luigi> after this error, which makes the exit message a bit confusing.
  Luigi> However, the above makes no sense---QuantLib::Calendar used to have
  Luigi> virtual functions, but this isn't true in the current release.
  Luigi> Maybe you are trying to compile QuantLib-Python with an older
  Luigi> version of QuantLib installed in /usr/include/ql?

I cannot exclude it, but I don't think this is likely. A build requires a set
of packages that are "essential for this build" to be installed. For
quantlib-python, this includes libquantlib0-dev.  The build environment is
then constituted based on the most current packages (from the "unstable"
branch) and we do indeed have 0.2.1 in there as the last line here shows:

edd@auric:~> madison libquantlib0-dev
libquantlib0-dev |    0.1.9-2 |      unstable | mips, mipsel
libquantlib0-dev |    0.2.0-1 |       testing | alpha, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc
libquantlib0-dev |    0.2.0-1 |      unstable | hurd-i386
libquantlib0-dev |    0.2.1-1 |      unstable | alpha, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc

Dirk

-- 
Good judgment comes from experience; experience comes from bad judgment. 
							    -- F. Brooks