problem compiling polybori (sage-4.2)

[François Bissey]

Hi,

I have a problem compiling polybori in sage-4.2.
I get the following:
g++ -o groebner/src/randomset.o -c -O3 -Wno-long-long -Wreturn-type -g -fPIC -
ftemplate-depth-100 -g -fPIC -O3 -Wno-long-long -Wreturn-type -g -fPIC -
DNDEBUG -DHAVE_GD -DHAVE_TR1_UNORDERED_MAP -DPACKED -DHAVE_M4RI -DHAVE_GD -
DHAVE_IEEE_754 -DBSD -I/media/anthill/portage/sci-
mathematics/sage-4.2/work/sage-4.2/spkg/build/polybori-0.6.3-20090827/src/boost_1_34_1.cropped
-I/media/anthill/portage/sci-mathematics/sage-4.2/work/sage-4.2/local/include
-I/media/anthill/portage/sci-
mathematics/sage-4.2/work/sage-4.2/local/include/python2.6 -Ipolybori/include
-ICudd/obj -ICudd/util -ICudd/cudd -ICudd/mtr -ICudd/st -ICudd/epd
groebner/src/randomset.cc
In file included from groebner/src/randomset.cc:12:
groebner/src/nf.h:23: error: variable or field 'drawmatrix' declared void
groebner/src/nf.h:23: error: 'mzd_t' was not declared in this scope
groebner/src/nf.h:23: error: 'mat' was not declared in this scope
groebner/src/nf.h:23: error: expected primary-expression before 'const'
scons: *** [groebner/src/randomset.o] Error 1
scons: building terminated because of errors.
Error building PolyBoRi.

Not sure why it happens. I am on gentoo on x86,
I tried with gcc-4.4.2 and gcc-3.4.3 with the same result,
Other info:
Host system
uname -a:
Linux vrooom 2.6.30-gentoo-r5 #1 Mon Aug 31 21:06:06 NZST 2009 i686 AMD
Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux
****************************************************
****************************************************
CC Version
gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /media/anthill/portage/sys-
devel/gcc-4.4.2/work/gcc-4.4.2/configure --prefix=/usr --bindir=/usr/i686-pc-
linux-gnu/gcc-bin/4.4.2 --includedir=/usr/lib/gcc/i686-pc-linux-
gnu/4.4.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.2 --
mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.2/man --
infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.2/info --with-gxx-include-
dir=/usr/lib/gcc/i686-pc-linux-gnu/4.4.2/include/g++-v4 --host=i686-pc-linux-
gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --with-
ppl --with-cloog --enable-nls --without-included-gettext --with-system-zlib --
disable-checking --disable-werror --enable-secureplt --disable-multilib --
enable-libmudflap --disable-libssp --disable-libgomp --enable-cld --with-
python-dir=/share/gcc-data/i686-pc-linux-gnu/4.4.2/python --disable-libgcj --
with-arch=i686 --enable-languages=c,c++,fortran --enable-shared --enable-
threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-
bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.4.2 p1.0'
Thread model: posix
gcc version 4.4.2 (Gentoo 4.4.2 p1.0)
****************************************************

[François Bissey]

I found the problem. I had an old of version of m4ri installed on my system
(20090105) and it was picked up by polybori. This version of m4ri lacks
mzd_t which lead to the error.

By the way it looks like the sage version of polybori doesn't depend on
libm4ri which means the internal copy is used (unless you perform an upgrade
which include a polybori version change). I thought the plan was to switch to
using the libm4ri spkg for polybori in sage long ago?

Francois

[Martin Albrecht]

On Sunday 01 November 2009, François Bissey wrote:
> By the way it looks like the sage version of polybori doesn't depend on
> libm4ri

Can you clarify what you mean by that? Do you mean in the Makefile?

> which means the internal copy is used (unless you perform an
> upgrade which include a polybori version change). I thought the plan was
> to switch to using the libm4ri spkg for polybori in sage long ago?

Martin

--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://www.informatik.uni-bremen.de/~malb
_jab: martinr...@jabber.ccc.de

[François Bissey]

On Sun, 01 Nov 2009 23:42:41 Martin Albrecht wrote:
> On Sunday 01 November 2009, François Bissey wrote:
> > By the way it looks like the sage version of polybori doesn't depend on
> > libm4ri
>
> Can you clarify what you mean by that? Do you mean in the Makefile?
>

The sage Makefile or more precisely "deps", for polybori it reads:
$(INST)/$(POLYBORI): $(BASE) $(INST)/$(PYTHON) $(INST)/$(SCONS)
$(INST)/$(BOOST_CROPPED)
$(SAGE_SPKG) $(POLYBORI) 2>&1

$(LIBM4RI) is pulled as a dependency of $(SAGE) after $(POLYBORI).
So in sage polybori will use its internal copy of m4ri (unless there
is a system copy like it happened to me).
However during a "sage -upgrade" if polybori is updated it is very
likely it will use the sage copy of m4ri.

Francois

[Martin Albrecht]

> The sage Makefile or more precisely "deps", for polybori it reads:
> $(INST)/$(POLYBORI): $(BASE) $(INST)/$(PYTHON) $(INST)/$(SCONS)
> $(INST)/$(BOOST_CROPPED)
> $(SAGE_SPKG) $(POLYBORI) 2>&1
>
> $(LIBM4RI) is pulled as a dependency of $(SAGE) after $(POLYBORI).
> So in sage polybori will use its internal copy of m4ri (unless there
> is a system copy like it happened to me).
> However during a "sage -upgrade" if polybori is updated it is very
> likely it will use the sage copy of m4ri.

Thanks,

I've uploaded a new deps file to

http://trac.sagemath.org/sage_trac/ticket/7271