Re: Pari module build failure
Bruno Haible <[email protected]> Mon, 22 Jan 2018 23:48:36 +0100
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <5726429.mKV3LjGoDc@omega> |
Hi Sam, > 1. mark tip as bad: ... Thanks a lot for the recipe! > 4. get this after 6 iterations: > > The first bad revision is: > changeset: 16442:a3806e5f96d1 > user: Bruno Haible <[email protected]> > date: Mon Jan 15 00:24:23 2018 +0100 > summary: Enable most optimizations on Mac OS X/x86_64. Oh really?! It looked like, from looking at the build-*/cbcstep3.log files, that these optimizations are safe. > Lesson learned: one cannot be really sure about an optimization without > testing modules too. Ack. > I will enable the modules tests in configure. Please enable only base-mod-check for the moment. Reason: Distros will usually enable some more modules than the 4 BASE_MODULES. But the other modules after often not up-to-date, and I wouldn't want that the packagers of clisp think that clisp by itself does not pass its testsuite. Or if you really want to enable full-mod-check, please do so in a different step (cbcstep5.log), so that's easy to distinguish these test failures from those in clisp proper. Bruno ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel