Poly/ML December 2006

polyml@lists.polyml.org

5 participants
4 discussions

polyml 5 heap option
by obua＠in.tum.de 14 Dec '06

14 Dec '06

Hi, I am using poly ml 5 together with Isabelle. When I start poly with the "-H 500" option, my process will terminate with a "run out of store" message after these 500MB have been used up (I used "top" to monitor the heap usage). If I give "-H 8000", it will succeed. Is this behaviour to be expected? Best, Steven -- Steven Obua Technische Universit?t M?nchen Institut f?r Informatik Boltzmannstr. 3 D-85748 Garching Tel: ++49 (0)89 / 289-17328 EMail: obua(a)in.tum.de Raum: 01.11.059

2 1

libtool -release option
by David.Matthews＠prolingua.co.uk 11 Dec '06

11 Dec '06

Ian Zimmerman wrote: > David> Ian, Since this is the first release of Poly/ML to use shared > David> libraries I would prefer to give this some thought now and then > David> adopt a scheme that can be used for future releases rather than > David> try and change it in the future. I don't have any strong > David> feelings either way and you obviously have some experience. > David> Would it be best to use -version-info 0:0:0 for this release? > > David> Because of the way the interface between compiled ML code and the > David> Poly/ML run-time library works I'll have to think about how > David> future releases should increment the version-info. > > The question is if it makes sense to upgrade the runtime and standalone > executables produced by linking with it independently. Not only for > end users, but also for distributions. > > If it does (and I think it does), then -version-info > will allow that and is preferable. The rules for incrementing the numbers > are spelled out in > > http://www.gnu.org/software/libtool/manual.html#Updating-version-info I thought about this and I've now made this change and updated CVS. The initial version is now 0:0 which is what the libtool manual suggests as the starting value. I hope that makes things simpler for Debian. David.

1 0

libtool -release option
by itz＠madbat.mine.nu 11 Dec '06

11 Dec '06

Is there a reason why this is used for libpolyml in the beta sources, instead of the -version-info or -version-number options as recommended by libtool manual? I am debianizing and lintian objects hard. -- Experience with Asset Control an asset.

2 3

Error while building PolyML 5.0 on Cygwin
by MichaelNedzelsky＠yandex.ru 10 Dec '06

10 Dec '06

After ./configure I tried to invoke make and get the following: --------------------------------------------------------------------------- $ make make all-recursive make[1]: Entering directory `/cygdrive/c/user/michael/polyml' Making all in libpolyml make[2]: Entering directory `/cygdrive/c/user/michael/polyml/libpolyml' if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT mpoly.lo -MD -MP -MF ".de ps/mpoly.Tpo" -c -o mpoly.lo mpoly.cpp; \ then mv -f ".deps/mpoly.Tpo" ".deps/mpoly.Plo"; else rm -f ".deps/mpoly.Tpo"; exit 1; fi mkdir .libs g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT mpoly.lo -MD -MP -MF .deps/mpoly.Tpo -c mpoly.cpp -DPIC -o .libs/mpoly.o g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT mpoly.lo -MD -MP -MF .deps/mpoly.Tpo -c mpoly.cpp -o mpoly.o >/dev/null 2> &1 if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT gc.lo -MD -MP -MF ".deps/ gc.Tpo" -c -o gc.lo gc.cpp; \ then mv -f ".deps/gc.Tpo" ".deps/gc.Plo"; else rm -f ".deps/gc.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT gc.lo -MD -MP -MF .deps/gc.Tpo -c gc.cpp -DPIC -o .libs/gc.o g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT gc.lo -MD -MP -MF .deps/gc.Tpo -c gc.cpp -o gc.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT diagnostics.lo -MD -MP -M F ".deps/diagnostics.Tpo" -c -o diagnostics.lo diagnostics.cpp; \ then mv -f ".deps/diagnostics.Tpo" ".deps/diagnostics.Plo"; else rm -f ".deps/diagnostics.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT diagnostics.lo -MD -MP -MF .deps/diagnostics.Tpo -c diagnostics.cpp -DPIC -o .libs/diagnostics.o g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT diagnostics.lo -MD -MP -MF .deps/diagnostics.Tpo -c diagnostics.cpp -o dia gnostics.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT arb.lo -MD -MP -MF ".deps /arb.Tpo" -c -o arb.lo arb.cpp; \ then mv -f ".deps/arb.Tpo" ".deps/arb.Plo"; else rm -f ".deps/arb.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT arb.lo -MD -MP -MF .deps/arb.Tpo -c arb.cpp -DPIC -o .libs/arb.o g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT arb.lo -MD -MP -MF .deps/arb.Tpo -c arb.cpp -o arb.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT reals.lo -MD -MP -MF ".de ps/reals.Tpo" -c -o reals.lo reals.cpp; \ then mv -f ".deps/reals.Tpo" ".deps/reals.Plo"; else rm -f ".deps/reals.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -Di386 -DLINUX -Wall -g -O3 -MT reals.lo -MD -MP -MF .deps/reals.Tpo -c reals.cpp -DPIC -o .libs/reals.o In file included from reals.cpp:59: /usr/include/ieeefp.h:185: error: previous declaration of `int isnan(double)' with C++ linkage /usr/include/math.h:125: error: conflicts with new declaration with C linkage /usr/include/ieeefp.h:186: error: previous declaration of `int isinf(double)' with C++ linkage /usr/include/math.h:126: error: conflicts with new declaration with C linkage /usr/include/ieeefp.h:187: error: previous declaration of `int finite(double)' with C++ linkage /usr/include/math.h:127: error: conflicts with new declaration with C linkage /usr/include/ieeefp.h:191: error: previous declaration of `int isnanf(float)' with C++ linkage /usr/include/math.h:240: error: conflicts with new declaration with C linkage /usr/include/ieeefp.h:192: error: previous declaration of `int isinff(float)' with C++ linkage /usr/include/math.h:241: error: conflicts with new declaration with C linkage /usr/include/ieeefp.h:193: error: previous declaration of `int finitef(float)' with C++ linkage /usr/include/math.h:242: error: conflicts with new declaration with C linkage make[2]: *** [reals.lo] Error 1 make[2]: Leaving directory `/cygdrive/c/user/michael/polyml/libpolyml' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/c/user/michael/polyml' make: *** [all] Error 2 --------------------------------------------------------------------------- On Linux (Mandrake 10.1) the CVS version of PolyML works fine. Regards, Michael Nedzelsky

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML December 2006