Juan Francisco Cantero Hurtado <[email protected]> writes: > On Mon, Aug 05, 2019 at 04:04:37PM +0100, Stuart Henderson wrote: > >> On 2019/08/05 17:25, Timo Myyrä wrote: >> > Juan Francisco Cantero Hurtado <[email protected]> writes: >> > >> > > On Sun, Aug 04, 2019 at 09:15:58PM +0100, Stuart Henderson wrote: >> > > >> > >> On 2019/08/04 22:00, Antoine Jacoutot wrote: >> > >> > I don't want to hijack this thread, but I just wanted to say that >> > >> > there are many >> > >> > wolves hiding. >> > >> > That gerbil port has *never* built successfully for me on exopi >> > >> > (amd64) since >> > >> > its first import. >> > >> >> > >> Thanks, glad it's not just me! >> > >> >> > >> > >> > >> > cc -O2 -pipe -Wno-unused -Wno-write-strings >> > >> > -Wdisabled-optimization -fwrapv -fno-strict-aliasing >> > >> > -fno-math-errno -fomit-frame-pointer -fPIC -fno-common -rdynamic >> > >> > -I"/usr/local/include/gambit" -o "gxpkg" gxpkg_.o gxpkg.o >> > >> > "/usr/local/lib/gambit/libgambit.a" -lutil -lm >> > >> > -L/usr/local/opt/openssl/lib -lssl -lcrypto >> > >> > [*] Build gerbil tags >> > >> > *** ERROR; build failed >> > >> > >> > >> > And thank you gerbil for the useless output... >> > >> >> > >> That is all I get from the default build, but if I run the "Build gerbil >> > >> tags" part manually I get the extra bits I showed. (I don't know why it >> > >> doesn't display this as part of a ports build though...it's running >> > >> the same script!) >> > >> >> > >> Perhaps there is something cpu dependent, I don't see any -march bits >> > >> in gerbil/gambit, though there are some cpuid instructions used in asm >> > >> in >> > >> gambit..basically 0 idea though. >> > >> >> > > >> > > That's part of the native backend and is not enabled by default. >> > > >> > > Could you test this patch?. >> > > >> > > >> > > diff --git Makefile Makefile >> > > index 88a777f7c30..7547cf59c6c 100644 >> > > --- Makefile >> > > +++ Makefile >> > > @@ -39,7 +39,8 @@ NO_TEST = Yes >> > > GERBIL_ROOT = ${PREFIX}/gerbil >> > > >> > > do-build: >> > > - cd ${WRKSRC}/src && ulimit -n 1024 && ${SETENV} ${MAKE_ENV} >> > > ./build.sh >> > > + cd ${WRKSRC}/src && ulimit -n 1024 -s 16384 && \ >> > > + ${SETENV} ${MAKE_ENV} ./build.sh >> > > >> > > do-install: >> > > ${INSTALL_DATA_DIR} ${GERBIL_ROOT} >> >> Trying that in my next build (though it would seem odd for it to require >> more stack on one machine than another?) > > Yes, really odd. The next test would be to change the compiler to gcc. I > would like to avoid that because gambit is really hard with the C > compilers and a good test bed for the clang upgrades. > >> >> > Another diff try as well on problem machines to enable running std tests: >> > >> > Index: Makefile >> > =================================================================== >> > RCS file: /cvs/ports/lang/gerbil/Makefile,v >> > retrieving revision 1.7 >> > diff -u -p -u -p -r1.7 Makefile >> > --- Makefile 12 Jul 2019 20:47:18 -0000 1.7 >> > +++ Makefile 5 Aug 2019 14:23:35 -0000 >> > @@ -34,8 +34,6 @@ MAKE_ENV += CPPFLAGS=-I${LOCALBASE}/incl >> > GERBIL_PATH=${WRKINST}${PREFIX}/gerbil \ >> > GAMBCOMP_VERBOSE=1 >> > >> > -NO_TEST = Yes >> > - >> > GERBIL_ROOT = ${PREFIX}/gerbil >> > >> > do-build: >> > @@ -48,5 +46,8 @@ do-install: >> > ${INSTALL_DATA} ${WRKSRC}/etc/gerbil.el >> > ${PREFIX}/share/emacs/site-lisp >> > ${INSTALL_DATA} ${WRKSRC}/*.md ${GERBIL_ROOT} >> > ${INSTALL_DATA} ${WRKSRC}/*.txt ${GERBIL_ROOT} >> > + >> > +do-test: >> > + ${SETENV} ${MAKE_ENV} ${WRKSRC}/bin/gxi >> > ${WRKSRC}/src/std/run-tests.ss >> > >> > .include <bsd.port.mk> >> >> Seems useful to have anyone, but do-test depends on build, so it won't be >> runnable on this machine. > > Timo, I can commit the patch if you want. We usually like to have the > tests enabled where possible.
Yeah, that can be committed in any case. Timo
