Poly/ML October 2020

polyml@lists.polyml.org

9 participants
10 discussions

Updates in git master including major change to FFI
by David.Matthews＠prolingua.co.uk 11 Mar '21

11 Mar '21

Hi, I've just pushed a collection of changes to master that have been in the pipeline for quite a long time. Some of these are internal changes to the run-time system and some are extensions, such as the addition of IPv6 networking with INet6Sock and Net6HostDB structures. The major change, though, is with the foreign function interface. On X86 platforms libffi is no longer used and the version of it included in the libpolyml directory has been removed. Libffi is still used in the interpreted version but only if the library is installed on the system. Instead the foreign function interface is handled essentially as part of the compiler. The high-level interface in the Foreign structure remains unchanged but the buildCallN functions now actually compile interface functions. This results in foreign function calls being substantially faster than with libffi; at least 10 times faster for trivial calls on the X86/64. The cost is, of course, some extra work when buildCallN is called, meaning that it is essential that these functions are only used at the top level. The reason for the speed-up is that the interface has to place the arguments in the correct registers for the ABI and the rules for placing arguments can be quite complicated, particular on the X86/64 on Unix. Libffi computes the placement on every call whereas the compiler can do this once and build code that moves the arguments into the right registers and returns the result. For backwards compatibility buildClosureN functions have been retained but these are wrappers around new buildCallback functions. The buildCallback functions differ in two respects. Closures created with buildCallback are garbage-collected which means that if they are used to register callbacks with a C library it may be necessary to keep a reference in ML. There is a touchClosure function that should be called when the callback is no longer needed. For compatibility closures created with buildClosure are retained in a global list to avoid garbage collection. The other difference is that the buildCallback functions have a slightly different type from buildClosure and that reflects the underlying implementation. For example, val buildCallback1: 'a conversion * 'b conversion -> ('a -> 'b) -> ('a -> 'b) closure The first application builds the interface code that handle the conversion between the ML and C ABIs. The second application applies this to an ML function to build a closure value that can be passed to C. This second application builds a small additional piece of code that simply loads the address of the ML function into a register and jumps to the interface code. What this means is that while the first application should always be done at the top level it is possible to embed an application of this to a particular ML function inside ML code. There is still an overhead compared with creating a closure in ML and it is better if possible to do the application at the top level but the cost is significantly less than if the whole buildCallback function were called within a function. As always please give this a try and let me know if there are problems. Regards, David

4 22

Can't build trunk (cea4c79c) on macOS 10.15
by binghe.lisp＠gmail.com 29 Oct '20

29 Oct '20

Hi, when I try to build latest polyml trunk (master) on macOS 10.15, I got the following errors: Making all in libpolyml /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O3 -DMACOSX -DGIT_VERSION=\"v5.8.1-286-gcea4c79c\" -Wall -DMODULEDIR=\"/usr/local/lib/polyml/modules\" -DMACOSX -MT x86assembly_gas64.lo -MD -MP -MF .deps/x86assembly_gas64.Tpo -c -o x86assembly_gas64.lo x86assembly_gas64.S libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O3 -DMACOSX -DGIT_VERSION=\"v5.8.1-286-gcea4c79c\" -Wall -DMODULEDIR=\"/usr/local/lib/polyml/modules\" -DMACOSX -MT x86assembly_gas64.lo -MD -MP -MF .deps/x86assembly_gas64.Tpo -c x86assembly_gas64.S -fno-common -DPIC -o .libs/x86assembly_gas64.o x86assembly_gas64.S:223:5: error: unsupported symbol modifier in branch relocation call X86TrapHandler at plt ^ make[2]: *** [x86assembly_gas64.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 My last (successful) build was: Poly/ML 5.8.2 Testing (Git version v5.8.1-68-gb4786634). GCC is from Xcode 12.1: $ gcc -v Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1 Apple clang version 12.0.0 (clang-1200.0.32.21) Target: x86_64-apple-darwin19.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin Please let me know if any further information is needed. Regards, Chun Tian

2 2

Install to users home directory
by dtopham＠gmail.com 20 Oct '20

20 Oct '20

I know it is most efficient to install software system wide so all users share same code. But I have a situation where I want to install only to my home directory. i.e. It is Linux system where I don't have sudo privilege. Is that possible? I am building from source, so perhaps ./configure --prefix=$HOME make make install Or does polyml have too many dependencies on other system libraries to make that impractical?

4 6

Install to users home directory
by dtopham＠gmail.com 20 Oct '20

20 Oct '20

Thanks Phil, I found I needed to set LD_LIBRARY_PATH as well as PATH to $HOME to use interpreter. I really appreciate the helpful information from this community! On Tue, Oct 20, 2020 at 4:00 AM <polyml-request at inf.ed.ac.uk> wrote: > Send polyml mailing list submissions to > polyml at inf.ed.ac.uk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > or, via email, send a message with subject or body 'help' to > polyml-request at inf.ed.ac.uk > > You can reach the person managing the list at > polyml-owner at inf.ed.ac.uk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of polyml digest..." > > > Today's Topics: > > 1. Re: Install to users home directory (Phil Clayton) > 2. Re: polyml install to Alpine Linux (David Matthews) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Oct 2020 10:12:37 +0100 > From: Phil Clayton <phil.clayton at veonix.com> > To: polyml at inf.ed.ac.uk > Subject: Re: [polyml] Install to users home directory > Message-ID: <090b6bb7-106a-eb9e-0732-2b00a050ebee at veonix.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 20/10/20 05:40, David Topham wrote: > > I know it is most efficient to install software system wide so all users > > share same code. But I have a situation where I want to install only to > > my home directory. i.e. It is Linux system where I don't have sudo > > privilege. > > Is that possible? > > I am building from source, so perhaps > > ./configure ?--prefix=$HOME > > make > > make install > > > > Or does polyml have too many dependencies on other system libraries to > > make that impractical? > > You can specify any prefix to install to - this does not affect how > dependencies are found. However, depending on your choice of prefix, > you may need to manually add <prefix>/bin to PATH. Depending on your > Linux distribution, it would probably be more idiomatic to do a per-user > install to > $HOME/.local > to avoid cluttering the home directory. Also, if you have Poly/ML > installed system-wide via the package manager, you would need to make > sure that <prefix>/bin occurs in the path before the system bin > directory, to ensure your user version is found first. > > There are some instructions previously posted here: > http://lists.inf.ed.ac.uk/pipermail/polyml/2017-July/002038.html > which also show how to disable the package manager version of Poly/ML on > Fedora. > > Phil > > > ------------------------------ > > Message: 2 > Date: Tue, 20 Oct 2020 11:56:55 +0100 > From: David Matthews <David.Matthews at prolingua.co.uk> > To: polyml at inf.ed.ac.uk > Subject: Re: [polyml] polyml install to Alpine Linux > Message-ID: <5bca1bc6-063e-b199-65f1-31e259038413 at prolingua.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 19/10/2020 21:08, David Matthews wrote: > >> Yes, using .data.rel.ro., i.e. relocatable read-only data. > > > > Thanks, Jess.? That seems to work, at least on SELinux and Alpine. > > OpenBSD seems to still want it to be writeable. > > I've now changed the ELF exporter to write the data to .data.rel.ro. > The byte code interpreted version (--disable-native-codegeneration) now > builds without a problem on Alpine Linux and on SELinux with hardening > turned on. That isn't a complete solution because it doesn't deal with > native code but it does show that if code could be handled everything > else will work. > > I see this primarily as future-proofing Poly/ML. It's not unlikely that > a future release of, say Mac OS X, might outlaw TEXTRELs. > > David > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > polyml mailing list > polyml at inf.ed.ac.uk > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > > ------------------------------ > > End of polyml Digest, Vol 168, Issue 9 > ************************************** > > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > >

3 2

polyml install to Alpine Linux
by dtopham＠gmail.com 20 Oct '20

20 Oct '20

I noticed same error seemed to have occurred from user installing to gentoo Linux. I can't tell from this if it was resolved or not (I'm relatively inexperienced) https://bugs.gentoo.org/713178 One thing in common between Alpine and this environment is they are using musl libc Could that be an issue?

4 7

polyml install to Alpine Linux
by dtopham＠gmail.com 18 Oct '20

18 Oct '20

Thanks Stefan! Brilliant! It is so nice to have a supportive community to build software with! That did it: no-pie On Sat, Oct 17, 2020 at 2:41 PM <polyml-request at inf.ed.ac.uk> wrote: > Send polyml mailing list submissions to > polyml at inf.ed.ac.uk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > or, via email, send a message with subject or body 'help' to > polyml-request at inf.ed.ac.uk > > You can reach the person managing the list at > polyml-owner at inf.ed.ac.uk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of polyml digest..." > > > Today's Topics: > > 1. Re: polyml Digest, Vol 168, Issue 4 (David Topham) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 17 Oct 2020 14:39:11 -0700 > From: David Topham <dtopham at gmail.com> > To: polyml at inf.ed.ac.uk > Subject: Re: [polyml] polyml Digest, Vol 168, Issue 4 > Message-ID: > <CAD034BFJRPsZzodxyX3iE5O+V-_E81p=+ > sbPr9PJxowMS6hZ+g at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Thank you for the quick response. That is useful to know. Perhaps my > original download of source was corrupt. I tried again this time use the > polyml-master.zip *from github" and that made it much further. > > I think it may be almost complete, but got a segment fault at the last > minute. > > make all-recursive > make[1]: Entering directory '/root/polyml-master' > Making all in libpolyml > make[2]: Entering directory '/root/polyml-master/libpolyml' > Making all in libffi > make[3]: Entering directory '/root/polyml-master/libpolyml/libffi' > make 'AR_FLAGS=' 'CC_FOR_BUILD=' 'CFLAGS=-O3 -fomit-frame-pointer > -fstrict-aliasing -ffast-math -march=pentium -Wall -fexceptions' > 'CXXFLAGS=-g -O2' 'CFLAGS_FOR_BUILD=' 'CFLAGS_FOR_TARGET=' > 'INSTALL=/usr/bin/install -c' 'INSTALL_DATA=/usr/bin/install -c -m 644' > 'INSTALL_PROGRAM=/usr/bin/install -c' 'INSTALL_SCRIPT=/usr/bin/install -c' > 'JC1FLAGS=' 'LDFLAGS=' 'LIBCFLAGS=' 'LIBCFLAGS_FOR_TARGET=' 'MAKE=make' > 'MAKEINFO=/bin/sh /root/polyml-master/libpolyml/libffi/missing makeinfo ' > 'PICFLAG=' 'PICFLAG_FOR_TARGET=' 'RUNTESTFLAGS=' 'SHELL=/bin/sh' > 'exec_prefix=/usr/local' 'infodir=/usr/local/share/info' > 'libdir=/usr/local/lib' 'mandir=/usr/local/share/man' 'prefix=/usr/local' > 'AR=ar' 'AS=as' 'CC=gcc' 'CXX=g++' 'LD=/usr/i586-alpine-linux-musl/bin/ld' > 'NM=/usr/bin/nm -B' 'RANLIB=ranlib' 'DESTDIR=' all-recursive > make[4]: Entering directory '/root/polyml-master/libpolyml/libffi' > Making all in include > make[5]: Entering directory '/root/polyml-master/libpolyml/libffi/include' > make[5]: Nothing to be done for 'all'. > make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/include' > Making all in testsuite > make[5]: Entering directory > '/root/polyml-master/libpolyml/libffi/testsuite' > make[5]: Nothing to be done for 'all'. > make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/testsuite' > Making all in man > make[5]: Entering directory '/root/polyml-master/libpolyml/libffi/man' > make[5]: Nothing to be done for 'all'. > make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/man' > make[5]: Entering directory '/root/polyml-master/libpolyml/libffi' > make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi' > make[4]: Leaving directory '/root/polyml-master/libpolyml/libffi' > make[3]: Leaving directory '/root/polyml-master/libpolyml/libffi' > make[3]: Entering directory '/root/polyml-master/libpolyml' > make[3]: Nothing to be done for 'all-am'. > make[3]: Leaving directory '/root/polyml-master/libpolyml' > make[2]: Leaving directory '/root/polyml-master/libpolyml' > Making all in libpolymain > make[2]: Entering directory '/root/polyml-master/libpolymain' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/root/polyml-master/libpolymain' > Making all in . > make[2]: Entering directory '/root/polyml-master' > make[2]: Leaving directory '/root/polyml-master' > Making all in modules > make[2]: Entering directory '/root/polyml-master/modules' > Making all in IntInfAsInt > make[3]: Entering directory '/root/polyml-master/modules/IntInfAsInt' > echo "use \"./ROOT.sml\";" | ../../poly -q -error-exit > Segmentation fault > make[3]: *** [Makefile:479: IntInfAsInt] Error 139 > make[3]: Leaving directory '/root/polyml-master/modules/IntInfAsInt' > make[2]: *** [Makefile:377: all-recursive] Error 1 > make[2]: Leaving directory '/root/polyml-master/modules' > make[1]: *** [Makefile:729: all-recursive] Error 1 > make[1]: Leaving directory '/root/polyml-master' > make: *** [Makefile:488: all] Error 2 > > On Sat, Oct 17, 2020 at 4:00 AM <polyml-request at inf.ed.ac.uk> wrote: > > > Send polyml mailing list submissions to > > polyml at inf.ed.ac.uk > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > > or, via email, send a message with subject or body 'help' to > > polyml-request at inf.ed.ac.uk > > > > You can reach the person managing the list at > > polyml-owner at inf.ed.ac.uk > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of polyml digest..." > > > > > > Today's Topics: > > > > 1. building polyml on Alpine Linux (David Topham) > > 2. Re: PolyML REPL (Anton Lobach) > > 3. Re: building polyml on Alpine Linux (David Matthews) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 16 Oct 2020 15:17:37 -0700 > > From: David Topham <dtopham at gmail.com> > > To: polyml at inf.ed.ac.uk > > Subject: [polyml] building polyml on Alpine Linux > > Message-ID: > > < > > CAD034BH36eK--zKkho2iYUi4x6Ar+7qjg28Le3T-NfS+Js-pTQ at mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > I have been trying to get polyml working on Alpine Linux 32-bit > > > > Since there is't yet a package to install it, I tried getting the source > > from github > > > > When doing make, I first got error about missing libffi directory. > > > > I thought I may bypass that by configuring with option to use system > libffi > > i.e. > > apk add libffi-dev > > ./configure --with-system-libffi --with-x > > > > Here is result: > > > > ---------------- > > make all-recursive > > make[1]: Entering directory '/root/vfpub/polyml-master' > > Making all in libpolyml > > make[2]: Entering directory '/root/vfpub/polyml-master/libpolyml' > > make[3]: Entering directory '/root/vfpub/polyml-master/libpolyml' > > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. > > -I.. -O3 -Wall -DMODULEDIR=\"/usr/local/lib/polyml/modules\" -O3 -MT > > arb.lo -MD -MP -MF .deps/arb.Tpo -c -o arb.lo arb.cpp > > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -O3 -Wall > > "-DMODULEDIR=\"/usr/local/lib/polyml/modules\"" -O3 -MT arb.lo -MD -MP > -MF > > .deps/arb.Tpo -c arb.cpp -fPIC -DPIC -o .libs/arb.o > > arb.cpp:87:10: fatal error: globals.h: No such file or directory > > 87 | #include "globals.h" > > | ^~~~~~~~~~~ > > compilation terminated. > > make[3]: *** [Makefile:800: arb.lo] Error 1 > > make[3]: Leaving directory '/root/vfpub/polyml-master/libpolyml' > > make[2]: *** [Makefile:840: all-recursive] Error 1 > > make[2]: Leaving directory '/root/vfpub/polyml-master/libpolyml' > > make[1]: *** [Makefile:729: all-recursive] Error 1 > > make[1]: Leaving directory '/root/vfpub/polyml-master' > > make: *** [Makefile:488: all] Error 2 > > --------------------------- > > > > Has anyone had luck building on Alpine? > >

1 0

polyml Digest, Vol 168, Issue 4
by dtopham＠gmail.com 17 Oct '20

17 Oct '20

Thank you for the quick response. That is useful to know. Perhaps my original download of source was corrupt. I tried again this time use the polyml-master.zip *from github" and that made it much further. I think it may be almost complete, but got a segment fault at the last minute. make all-recursive make[1]: Entering directory '/root/polyml-master' Making all in libpolyml make[2]: Entering directory '/root/polyml-master/libpolyml' Making all in libffi make[3]: Entering directory '/root/polyml-master/libpolyml/libffi' make 'AR_FLAGS=' 'CC_FOR_BUILD=' 'CFLAGS=-O3 -fomit-frame-pointer -fstrict-aliasing -ffast-math -march=pentium -Wall -fexceptions' 'CXXFLAGS=-g -O2' 'CFLAGS_FOR_BUILD=' 'CFLAGS_FOR_TARGET=' 'INSTALL=/usr/bin/install -c' 'INSTALL_DATA=/usr/bin/install -c -m 644' 'INSTALL_PROGRAM=/usr/bin/install -c' 'INSTALL_SCRIPT=/usr/bin/install -c' 'JC1FLAGS=' 'LDFLAGS=' 'LIBCFLAGS=' 'LIBCFLAGS_FOR_TARGET=' 'MAKE=make' 'MAKEINFO=/bin/sh /root/polyml-master/libpolyml/libffi/missing makeinfo ' 'PICFLAG=' 'PICFLAG_FOR_TARGET=' 'RUNTESTFLAGS=' 'SHELL=/bin/sh' 'exec_prefix=/usr/local' 'infodir=/usr/local/share/info' 'libdir=/usr/local/lib' 'mandir=/usr/local/share/man' 'prefix=/usr/local' 'AR=ar' 'AS=as' 'CC=gcc' 'CXX=g++' 'LD=/usr/i586-alpine-linux-musl/bin/ld' 'NM=/usr/bin/nm -B' 'RANLIB=ranlib' 'DESTDIR=' all-recursive make[4]: Entering directory '/root/polyml-master/libpolyml/libffi' Making all in include make[5]: Entering directory '/root/polyml-master/libpolyml/libffi/include' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/include' Making all in testsuite make[5]: Entering directory '/root/polyml-master/libpolyml/libffi/testsuite' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/testsuite' Making all in man make[5]: Entering directory '/root/polyml-master/libpolyml/libffi/man' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi/man' make[5]: Entering directory '/root/polyml-master/libpolyml/libffi' make[5]: Leaving directory '/root/polyml-master/libpolyml/libffi' make[4]: Leaving directory '/root/polyml-master/libpolyml/libffi' make[3]: Leaving directory '/root/polyml-master/libpolyml/libffi' make[3]: Entering directory '/root/polyml-master/libpolyml' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/root/polyml-master/libpolyml' make[2]: Leaving directory '/root/polyml-master/libpolyml' Making all in libpolymain make[2]: Entering directory '/root/polyml-master/libpolymain' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/root/polyml-master/libpolymain' Making all in . make[2]: Entering directory '/root/polyml-master' make[2]: Leaving directory '/root/polyml-master' Making all in modules make[2]: Entering directory '/root/polyml-master/modules' Making all in IntInfAsInt make[3]: Entering directory '/root/polyml-master/modules/IntInfAsInt' echo "use \"./ROOT.sml\";" | ../../poly -q -error-exit Segmentation fault make[3]: *** [Makefile:479: IntInfAsInt] Error 139 make[3]: Leaving directory '/root/polyml-master/modules/IntInfAsInt' make[2]: *** [Makefile:377: all-recursive] Error 1 make[2]: Leaving directory '/root/polyml-master/modules' make[1]: *** [Makefile:729: all-recursive] Error 1 make[1]: Leaving directory '/root/polyml-master' make: *** [Makefile:488: all] Error 2 On Sat, Oct 17, 2020 at 4:00 AM <polyml-request at inf.ed.ac.uk> wrote: > Send polyml mailing list submissions to > polyml at inf.ed.ac.uk > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > or, via email, send a message with subject or body 'help' to > polyml-request at inf.ed.ac.uk > > You can reach the person managing the list at > polyml-owner at inf.ed.ac.uk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of polyml digest..." > > > Today's Topics: > > 1. building polyml on Alpine Linux (David Topham) > 2. Re: PolyML REPL (Anton Lobach) > 3. Re: building polyml on Alpine Linux (David Matthews) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Oct 2020 15:17:37 -0700 > From: David Topham <dtopham at gmail.com> > To: polyml at inf.ed.ac.uk > Subject: [polyml] building polyml on Alpine Linux > Message-ID: > < > CAD034BH36eK--zKkho2iYUi4x6Ar+7qjg28Le3T-NfS+Js-pTQ at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I have been trying to get polyml working on Alpine Linux 32-bit > > Since there is't yet a package to install it, I tried getting the source > from github > > When doing make, I first got error about missing libffi directory. > > I thought I may bypass that by configuring with option to use system libffi > i.e. > apk add libffi-dev > ./configure --with-system-libffi --with-x > > Here is result: > > ---------------- > make all-recursive > make[1]: Entering directory '/root/vfpub/polyml-master' > Making all in libpolyml > make[2]: Entering directory '/root/vfpub/polyml-master/libpolyml' > make[3]: Entering directory '/root/vfpub/polyml-master/libpolyml' > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. > -I.. -O3 -Wall -DMODULEDIR=\"/usr/local/lib/polyml/modules\" -O3 -MT > arb.lo -MD -MP -MF .deps/arb.Tpo -c -o arb.lo arb.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -O3 -Wall > "-DMODULEDIR=\"/usr/local/lib/polyml/modules\"" -O3 -MT arb.lo -MD -MP -MF > .deps/arb.Tpo -c arb.cpp -fPIC -DPIC -o .libs/arb.o > arb.cpp:87:10: fatal error: globals.h: No such file or directory > 87 | #include "globals.h" > | ^~~~~~~~~~~ > compilation terminated. > make[3]: *** [Makefile:800: arb.lo] Error 1 > make[3]: Leaving directory '/root/vfpub/polyml-master/libpolyml' > make[2]: *** [Makefile:840: all-recursive] Error 1 > make[2]: Leaving directory '/root/vfpub/polyml-master/libpolyml' > make[1]: *** [Makefile:729: all-recursive] Error 1 > make[1]: Leaving directory '/root/vfpub/polyml-master' > make: *** [Makefile:488: all] Error 2 > --------------------------- > > Has anyone had luck building on Alpine? >

1 0

building polyml on Alpine Linux
by dtopham＠gmail.com 17 Oct '20

17 Oct '20

I have been trying to get polyml working on Alpine Linux 32-bit Since there is't yet a package to install it, I tried getting the source from github When doing make, I first got error about missing libffi directory. I thought I may bypass that by configuring with option to use system libffi i.e. apk add libffi-dev ./configure --with-system-libffi --with-x Here is result: ---------------- make all-recursive make[1]: Entering directory '/root/vfpub/polyml-master' Making all in libpolyml make[2]: Entering directory '/root/vfpub/polyml-master/libpolyml' make[3]: Entering directory '/root/vfpub/polyml-master/libpolyml' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -O3 -Wall -DMODULEDIR=\"/usr/local/lib/polyml/modules\" -O3 -MT arb.lo -MD -MP -MF .deps/arb.Tpo -c -o arb.lo arb.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -O3 -Wall "-DMODULEDIR=\"/usr/local/lib/polyml/modules\"" -O3 -MT arb.lo -MD -MP -MF .deps/arb.Tpo -c arb.cpp -fPIC -DPIC -o .libs/arb.o arb.cpp:87:10: fatal error: globals.h: No such file or directory 87 | #include "globals.h" | ^~~~~~~~~~~ compilation terminated. make[3]: *** [Makefile:800: arb.lo] Error 1 make[3]: Leaving directory '/root/vfpub/polyml-master/libpolyml' make[2]: *** [Makefile:840: all-recursive] Error 1 make[2]: Leaving directory '/root/vfpub/polyml-master/libpolyml' make[1]: *** [Makefile:729: all-recursive] Error 1 make[1]: Leaving directory '/root/vfpub/polyml-master' make: *** [Makefile:488: all] Error 2 --------------------------- Has anyone had luck building on Alpine?

2 1

PolyML REPL
by antonlobach＠uri.edu 17 Oct '20

17 Oct '20

Hi, Does PolyML REPL produce native code or does it work as an interpreter? Regards, Anton Lobach

2 2

polyml sometimes runs out of memory with plenty available
by sorear＠fastmail.com 05 Oct '20

05 Oct '20

Attempting to run the CakeML CI test sequence (a 2-3 day process) on any Poly/ML version newer than 5.7 frequently results in out of memory errors. The probability of any given test failing is low and seems very sensitive to environmental factors, and I am still trying to reliably reproduce the failure in any setting, but I have managed to generate --debug gc --debug heapsize logs from failures (attached). The log file is from v5.8.1 but I have seen the issue on several different HEAD revisions over the past month. The "Run out of store - interrupting threads" message in the middle of a block of GC output makes me suspect a race condition but otherwise I have little to go on here. Any advice would be appreciated. I'll update if I find anything. The machine has 256GB installed and I generally run tests with --maxheap 75000, so a failure with a heap size of only 2GB is quite odd. -s

2 3

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 October 2020