Menu
▾
▴
clisp-devel — closed list for developers and testers
You can subscribe to this list here.
| 2000 |
Jan
(81) |
Feb
(55) |
Mar
(459) |
Apr
(159) |
May
(126) |
Jun
(69) |
Jul
(48) |
Aug
(29) |
Sep
(106) |
Oct
(76) |
Nov
(155) |
Dec
(161) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(122) |
Feb
(150) |
Mar
(294) |
Apr
(124) |
May
(197) |
Jun
(266) |
Jul
(111) |
Aug
(259) |
Sep
(163) |
Oct
(142) |
Nov
(101) |
Dec
(86) |
| 2002 |
Jan
(187) |
Feb
(108) |
Mar
(274) |
Apr
(157) |
May
(346) |
Jun
(242) |
Jul
(345) |
Aug
(187) |
Sep
(263) |
Oct
(69) |
Nov
(30) |
Dec
(76) |
| 2003 |
Jan
(125) |
Feb
(191) |
Mar
(87) |
Apr
(69) |
May
(107) |
Jun
(66) |
Jul
(112) |
Aug
(161) |
Sep
(184) |
Oct
(137) |
Nov
(28) |
Dec
(61) |
| 2004 |
Jan
(148) |
Feb
(99) |
Mar
(365) |
Apr
(225) |
May
(311) |
Jun
(204) |
Jul
(95) |
Aug
(214) |
Sep
(256) |
Oct
(290) |
Nov
(239) |
Dec
(152) |
| 2005 |
Jan
(253) |
Feb
(183) |
Mar
(178) |
Apr
(88) |
May
(175) |
Jun
(195) |
Jul
(122) |
Aug
(81) |
Sep
(119) |
Oct
(200) |
Nov
(110) |
Dec
(179) |
| 2006 |
Jan
(154) |
Feb
(64) |
Mar
(55) |
Apr
(69) |
May
(66) |
Jun
(64) |
Jul
(80) |
Aug
(59) |
Sep
(62) |
Oct
(90) |
Nov
(132) |
Dec
(106) |
| 2007 |
Jan
(58) |
Feb
(51) |
Mar
(59) |
Apr
(19) |
May
(33) |
Jun
(52) |
Jul
(15) |
Aug
(50) |
Sep
(41) |
Oct
(259) |
Nov
(323) |
Dec
(136) |
| 2008 |
Jan
(205) |
Feb
(128) |
Mar
(203) |
Apr
(126) |
May
(307) |
Jun
(166) |
Jul
(259) |
Aug
(181) |
Sep
(217) |
Oct
(265) |
Nov
(256) |
Dec
(132) |
| 2009 |
Jan
(104) |
Feb
(81) |
Mar
(27) |
Apr
(21) |
May
(85) |
Jun
(237) |
Jul
(243) |
Aug
(199) |
Sep
(178) |
Oct
(151) |
Nov
(64) |
Dec
(39) |
| 2010 |
Jan
(33) |
Feb
(146) |
Mar
(125) |
Apr
(109) |
May
(52) |
Jun
(135) |
Jul
(103) |
Aug
(68) |
Sep
(99) |
Oct
(88) |
Nov
(45) |
Dec
(56) |
| 2011 |
Jan
(19) |
Feb
(32) |
Mar
(50) |
Apr
(105) |
May
(46) |
Jun
(22) |
Jul
(101) |
Aug
(80) |
Sep
(52) |
Oct
(16) |
Nov
(10) |
Dec
(29) |
| 2012 |
Jan
(8) |
Feb
(22) |
Mar
(17) |
Apr
(68) |
May
(19) |
Jun
(19) |
Jul
(12) |
Aug
(6) |
Sep
(13) |
Oct
(5) |
Nov
(5) |
Dec
(5) |
| 2013 |
Jan
(6) |
Feb
(4) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(16) |
Apr
(1) |
May
(8) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(8) |
Mar
(23) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
(5) |
| 2016 |
Jan
|
Feb
|
Mar
(16) |
Apr
(6) |
May
(53) |
Jun
(19) |
Jul
(3) |
Aug
(39) |
Sep
(24) |
Oct
(2) |
Nov
(19) |
Dec
|
| 2017 |
Jan
(13) |
Feb
(44) |
Mar
(208) |
Apr
(12) |
May
(94) |
Jun
(54) |
Jul
(18) |
Aug
(52) |
Sep
(12) |
Oct
(22) |
Nov
(27) |
Dec
(93) |
| 2018 |
Jan
(85) |
Feb
(28) |
Mar
(16) |
Apr
(47) |
May
(16) |
Jun
(15) |
Jul
(10) |
Aug
(3) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
|
| 2019 |
Jan
(4) |
Feb
(6) |
Mar
(12) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2022 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(10) |
Oct
(5) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(28) |
Dec
(3) |
| 2025 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bruno H. <br...@cl...> - 2017-03-20 09:30:33
|
Hi Reini, > intparam.h and floatparam.h clash, overwriting each others tmp.c > with parallel make. fixes https://github.com/rurban/clisp/issues/1 Thanks. I applied this with small modifications: For a file that generates foo, I prefer the name 'gen-foo.c' rather than 'footmp.c'. Bruno |
|
From: <cli...@li...> - 2017-03-20 09:28:54
|
Send clisp-cvs mailing list submissions to cli...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/clisp-cvs or, via email, send a message with subject or body 'help' to cli...@li... You can reach the person managing the list at cli...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of clisp-cvs digest..." CLISP CVS commits for today Today's Topics: 1. clisp: Fix build failure on Linux/arm. (cli...@li...) 2. clisp: Don't test unportable features in "make check". (cli...@li...) 3. clisp: Fix build failures with --with-debug on NetBSD. (cli...@li...) 4. clisp: Update to the newest gnulib. (cli...@li...) 5. clisp: Avoid code duplication of a condition. (cli...@li...) 6. clisp: Make --enable-portability enable support for any kind of ... (cli...@li...) 7. clisp: Update to the newest gnulib. (cli...@li...) 8. clisp: Fix an autoconf test crash on IA64. (cli...@li...) 9. clisp: Fix alignment issues on IA64 and with GENERIC64C_HEAPCODES. (cli...@li...) 10. clisp: Fix build failure when compiling 'newer' on Cygwin. (cli...@li...) 11. clisp: Fix error message when configure fails due to a missing a... (cli...@li...) 12. clisp: Don't generate a broken Makefile when using the option --... (cli...@li...) 13. clisp: Fix recognition of native Windows as target platform. (cli...@li...) 14. clisp: Fix the recognition of Solaris. (cli...@li...) 15. clisp: Prepare beta release. (cli...@li...) 16. clisp: Added tag clisp_2_49_50-2017-03-19 for changeset baa75d8e... (cli...@li...) 17. clisp: Bump version number after beta release. (cli...@li...) ---------------------------------------------------------------------- Message: 1 Date: Fri, 17 Mar 2017 22:14:20 +0000 From: cli...@li... Subject: clisp: Fix build failure on Linux/arm. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/950c54ba1ed8 changeset: 15843:950c54ba1ed82e4dcde30d2b680542476b4148c5 user: Bruno Haible <br...@cl...> date: 2017-03-17 10:47:20 +0100 description: Fix build failure on Linux/arm. diffstat: src/ChangeLog | 8 ++++++++ src/arilev0.d | 16 ++++++++++++++++ 2 files changed, 24 insertions(+), 0 deletions(-) ------------------------------ Message: 2 Date: Fri, 17 Mar 2017 22:14:21 +0000 From: cli...@li... Subject: clisp: Don't test unportable features in "make check". To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/934f6aa3ac13 changeset: 15844:934f6aa3ac13fea18df10dad97357cd8b86f5752 user: Bruno Haible <br...@cl...> date: 2017-03-17 23:13:25 +0100 description: Don't test unportable features in "make check". diffstat: src/ChangeLog | 6 ++++++ src/makemake.in | 46 +++++++++++++++++++++++++++++----------------- 2 files changed, 35 insertions(+), 17 deletions(-) ------------------------------ Message: 3 Date: Sat, 18 Mar 2017 01:09:40 +0000 From: cli...@li... Subject: clisp: Fix build failures with --with-debug on NetBSD. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/dc8e580f3ab6 changeset: 15845:dc8e580f3ab6d3dfcd82fe108d8dbc637a4a2066 user: Bruno Haible <br...@cl...> date: 2017-03-18 00:48:40 +0100 description: Fix build failures with --with-debug on NetBSD. diffstat: src/ChangeLog | 9 +++++++++ src/foreign.d | 2 +- src/lispbibl.d | 1 + src/unix.d | 7 ++++--- 4 files changed, 15 insertions(+), 4 deletions(-) ------------------------------ Message: 4 Date: Sat, 18 Mar 2017 01:09:44 +0000 From: cli...@li... Subject: clisp: Update to the newest gnulib. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6e1c388b7b75 changeset: 15846:6e1c388b7b75756231360514414af5932de6880f user: Bruno Haible <br...@cl...> date: 2017-03-18 01:19:22 +0100 description: Update to the newest gnulib. diffstat: src/ChangeLog | 9 +++++++++ src/aclocal.m4 | 9 ++++++--- src/configure | 9 ++++++--- src/gllib/stat-time.h | 8 ++++++++ src/gllib/stdalign.in.h | 2 +- src/gllib/stdint.in.h | 43 +++++++++++++++++++++++++++++++------------ src/gllib/timespec.h | 8 ++++++++ src/glm4/flexmember.m4 | 7 +++++-- src/glm4/stdalign.m4 | 2 +- 9 files changed, 75 insertions(+), 22 deletions(-) ------------------------------ Message: 5 Date: Sat, 18 Mar 2017 20:47:23 +0000 From: cli...@li... Subject: clisp: Avoid code duplication of a condition. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/e063cc84fc47 changeset: 15847:e063cc84fc478113ce2fb4c77abd7093271ad086 user: Bruno Haible <br...@cl...> date: 2017-03-18 10:07:13 +0100 description: Avoid code duplication of a condition. diffstat: src/ChangeLog | 9 +++++++++ src/constobj_tl.d | 2 +- src/lispbibl.d | 8 +++++--- src/spvw_global.d | 2 +- 4 files changed, 16 insertions(+), 5 deletions(-) ------------------------------ Message: 6 Date: Sat, 18 Mar 2017 20:47:24 +0000 From: cli...@li... Subject: clisp: Make --enable-portability enable support for any kind of ... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/fb70edea5256 changeset: 15848:fb70edea525656778462cf94f85abfcdb155347c user: Bruno Haible <br...@cl...> date: 2017-03-18 10:18:48 +0100 description: Make --enable-portability enable support for any kind of address space. diffstat: src/ChangeLog | 10 ++++++++++ src/lispbibl.d | 20 +++++++++++++++++--- src/makemake.in | 1 + 3 files changed, 28 insertions(+), 3 deletions(-) ------------------------------ Message: 7 Date: Sun, 19 Mar 2017 22:06:57 +0000 From: cli...@li... Subject: clisp: Update to the newest gnulib. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/27a6541a83cc changeset: 15849:27a6541a83ccb9adc5763691abedcfa8728f89fe user: Bruno Haible <br...@cl...> date: 2017-03-19 16:46:16 +0100 description: Update to the newest gnulib. diffstat: src/ChangeLog | 9 + src/aclocal.m4 | 4 +- src/configure | 6 +- src/gllib/glthread/lock.h | 4 +- src/gllib/stdalign.in.h | 2 +- src/gllib/vma-iter.c | 319 +++++++++++++++++++++++++++++++++++++++++---- src/gllib/vma-iter.h | 2 +- src/glm4/stdalign.m4 | 4 +- 8 files changed, 306 insertions(+), 44 deletions(-) ------------------------------ Message: 8 Date: Sun, 19 Mar 2017 22:06:58 +0000 From: cli...@li... Subject: clisp: Fix an autoconf test crash on IA64. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6bd5fc3f31c5 changeset: 15850:6bd5fc3f31c5ae6472940173736a7f79c584bc29 user: Bruno Haible <br...@cl...> date: 2017-03-19 20:54:26 +0100 description: Fix an autoconf test crash on IA64. diffstat: src/ChangeLog | 6 ++++++ src/m4/mmap.m4 | 7 +++++++ 2 files changed, 13 insertions(+), 0 deletions(-) ------------------------------ Message: 9 Date: Sun, 19 Mar 2017 22:07:00 +0000 From: cli...@li... Subject: clisp: Fix alignment issues on IA64 and with GENERIC64C_HEAPCODES. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d974fb7fa9c6 changeset: 15851:d974fb7fa9c6748236ac0d33f01e35b887f5d0b4 user: Bruno Haible <br...@cl...> date: 2017-03-19 21:01:44 +0100 description: Fix alignment issues on IA64 and with GENERIC64C_HEAPCODES. diffstat: src/ChangeLog | 17 +++++++++++ src/encoding.d | 6 ++-- src/lispbibl.d | 87 +++++++++++++++++++++++++++++++++++++++------------------ src/spvw.d | 40 +++++++++++++++++++------- 4 files changed, 108 insertions(+), 42 deletions(-) ------------------------------ Message: 10 Date: Sun, 19 Mar 2017 22:07:01 +0000 From: cli...@li... Subject: clisp: Fix build failure when compiling 'newer' on Cygwin. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/274e978b0d2b changeset: 15852:274e978b0d2b555072d46e563bcb02b5e784556a user: Bruno Haible <br...@cl...> date: 2017-03-19 21:44:05 +0100 description: Fix build failure when compiling 'newer' on Cygwin. diffstat: src/ChangeLog | 7 +++++++ src/makemake.in | 29 +++++++++++++---------------- 2 files changed, 20 insertions(+), 16 deletions(-) ------------------------------ Message: 11 Date: Sun, 19 Mar 2017 22:07:02 +0000 From: cli...@li... Subject: clisp: Fix error message when configure fails due to a missing a... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/07ae489d1bd5 changeset: 15853:07ae489d1bd564204bfcc84da3686421bedc4a40 user: Bruno Haible <br...@cl...> date: 2017-03-19 22:00:27 +0100 description: Fix error message when configure fails due to a missing argument. diffstat: configure | 4 ++-- src/ChangeLog | 6 ++++++ 2 files changed, 8 insertions(+), 2 deletions(-) ------------------------------ Message: 12 Date: Sun, 19 Mar 2017 22:07:04 +0000 From: cli...@li... Subject: clisp: Don't generate a broken Makefile when using the option --... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d9495d8cbbd1 changeset: 15854:d9495d8cbbd1bf023d4993de868c43110064fb52 user: Bruno Haible <br...@cl...> date: 2017-03-19 22:10:11 +0100 description: Don't generate a broken Makefile when using the option --host/--build. diffstat: configure | 6 ------ src/ChangeLog | 13 +++++++++++++ 2 files changed, 13 insertions(+), 6 deletions(-) ------------------------------ Message: 13 Date: Sun, 19 Mar 2017 22:07:05 +0000 From: cli...@li... Subject: clisp: Fix recognition of native Windows as target platform. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/41bcb2050c9a changeset: 15855:41bcb2050c9a3c6a4a8c923ff6a1b61bfb595742 user: Bruno Haible <br...@cl...> date: 2017-03-19 22:20:37 +0100 description: Fix recognition of native Windows as target platform. diffstat: src/ChangeLog | 5 +++++ src/makemake.in | 5 ++++- 2 files changed, 9 insertions(+), 1 deletions(-) ------------------------------ Message: 14 Date: Sun, 19 Mar 2017 22:07:06 +0000 From: cli...@li... Subject: clisp: Fix the recognition of Solaris. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/a819470122d4 changeset: 15856:a819470122d45d2a2c88f6d1f52c17129573647e user: Bruno Haible <br...@cl...> date: 2017-03-19 22:58:12 +0100 description: Fix the recognition of Solaris. diffstat: src/ChangeLog | 5 +++++ src/lispbibl.d | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) ------------------------------ Message: 15 Date: Sun, 19 Mar 2017 22:07:08 +0000 From: cli...@li... Subject: clisp: Prepare beta release. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/baa75d8eba03 changeset: 15857:baa75d8eba036a3f9b3088266a34a607266ae092 user: Bruno Haible <br...@cl...> date: 2017-03-19 22:26:44 +0100 description: Prepare beta release. diffstat: src/ChangeLog | 6 ++++++ src/aclocal.m4 | 7 +++++++ src/configure | 29 ++++++++++++++++++----------- src/version.h | 4 ++-- version.sh | 4 ++-- 5 files changed, 35 insertions(+), 15 deletions(-) ------------------------------ Message: 16 Date: Mon, 20 Mar 2017 01:29:01 +0000 From: cli...@li... Subject: clisp: Added tag clisp_2_49_50-2017-03-19 for changeset baa75d8e... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/a78ef2b24313 changeset: 15858:a78ef2b243131881517ddea45bc1dd04b57ee319 user: Bruno Haible <br...@cl...> date: 2017-03-20 02:13:08 +0100 description: Added tag clisp_2_49_50-2017-03-19 for changeset baa75d8eba03 diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) ------------------------------ Message: 17 Date: Mon, 20 Mar 2017 09:28:50 +0000 From: cli...@li... Subject: clisp: Bump version number after beta release. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/2b543c6e4552 changeset: 15859:2b543c6e4552216badeb8946515e1453cae1b95c user: Bruno Haible <br...@cl...> date: 2017-03-20 09:54:32 +0100 description: Bump version number after beta release. diffstat: src/ChangeLog | 6 ++++++ src/configure | 22 +++++++++++----------- src/version.h | 4 ++-- version.sh | 4 ++-- 4 files changed, 21 insertions(+), 15 deletions(-) ------------------------------ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 75, Issue 6 **************************************** |
|
From: Reini U. <rei...@gm...> - 2017-03-20 07:41:35
|
And found another one:
README, README.de, README.es, clisp.c, ... all clash
with parallel builds using the same intermediate
txt binaries and txt.c sources.
Rename them.
Use a $(( $i + 1 )) shell function, which should be portable across
all shells.
See https://github.com/rurban/clisp/issues/1
src/makemake.in | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
Reini Urban
ru...@cp...
> On Mar 20, 2017, at 8:01 AM, Reini Urban <rei...@gm...> wrote:
>
> intparam.h and floatparam.h clash, overwriting each others tmp.c
> with parallel make. fixes https://github.com/rurban/clisp/issues/1
> ---
> src/makemake.in | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> <0001-Fix-parallel-make-j4.patch>
>
> --
> Reini
>
>
|
|
From: Reini U. <rei...@gm...> - 2017-03-20 07:03:09
|
Like "End of comment outside comment in line" caused by multi-line comments not detected as such with #define. --- src/aridecl.d | 10 +++++----- src/lispbibl.d | 6 +++--- 2 files changed, 8 insertions(+), 8 deletions(-) |
|
From: Reini U. <rei...@gm...> - 2017-03-20 07:02:04
|
intparam.h and floatparam.h clash, overwriting each others tmp.c with parallel make. fixes https://github.com/rurban/clisp/issues/1 --- src/makemake.in | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) |
|
From: Reini U. <rei...@gm...> - 2017-03-20 06:51:25
|
Reini Urban ru...@cp... > On Mar 19, 2017, at 11:43 AM, Bruno Haible <br...@cl...> wrote: > > Hi Reini, > >> 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows). >> ... >> https://github.com/rurban/clisp/commit/7b64a9b41d74460dc361e117700eee9713601ea0 > > Can you make the builds work on a machine that has not only MSVC but also > Cygwin installed? Cygwin would be nice, esp. to produce releases, but I’m not sure if Appveyor provides such an image yet. They are just a small Russian company, not so high-powered as Travis in Berlin. First I wanted to get MSVC passing, then I wanted to switch over to mingw, which is supported, and smoke with win32 and win64. Eventually add a cygwin setup in a local cache, for much easier testing, but I haven’t done this yet in other projects. I have to look around. I gave up on cygwin locally some years ago, as I could switch fully to darwin/linux and do not maintain my windows machines anymore. Only eventually I’ll have to do that, most likely to debug libsigsegv on win64. This was the latest blocker when I left. > I'm asking because nowadays my preferred way to produce native Windows binaries > is by using Cygwin as a development environment, see [1], as it > - does not require to manually maintain a config.h (since it's fully > autoconfiguring), > - does not require the complexity in makemake.in regarding backslashes vs. > slashes (since the build relies on GNU make, not nmake), > - does not require to regularly update win32msvc/makefile.msvc* (the last > update was in 2010!) Yes. I explicitly wanted to catch some errors there, on such old platforms. Apparently I found some :) > In other words, is much much simpler. But it requires Cygwin tools. Or in the > future, the Microsoft WSL [2] may be reliable enough for this task as well. > > Bruno > > [1] http://git.savannah.gnu.org/gitweb/?p=libsigsegv.git;a=blob;f=README.windows > [2] https://msdn.microsoft.com/en-us/commandline/wsl/about > |
|
From: Bruno H. <br...@cl...> - 2017-03-19 22:11:44
|
Hi, With the recent progress in build failure elimination on various platforms, I've made a beta release at https://haible.de/bruno/gnu/clisp-2.49.50.tar.bz2 You can give it out to testers, on the condition to remind them that - It's a not a full release, but rather a work-in-progress towards a release. - They must configure with --enable-portability. - Report all problems to this mailing list, so that we can fix them. Bruno |
|
From: <don...@is...> - 2017-03-19 19:09:25
|
Bruno Haible writes:
> Don Cohen wrote:
> > I now try creating a new version of Makefile.devel containing
> > MULTIBUILD_OPTIONS = --with-threads=POSIX_THREADS
> >
> > I hope you see some useful pattern in the following output:
> >
> > $ ls -l build-*/cbcstep3.log
...
> I can't spot the pattern, no. It would be good to extract a one-line summary
> of each such log file (OK vs. KO with error message).
1743 build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log
./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW -lp ../src/ -x '(and (load "../src/init.lisp") (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
Makefile:1428: recipe for target 'interpreted.mem' failed
make[1]: *** [interpreted.mem] Segmentation fault (core dumped)
1679 build-porting64-gcc-generational_gc-old_gc/cbcstep3.log
same as above
4766685 build-porting64-gcc-generic64_heapcodes/cbcstep3.log
37 streams: 1 error out of 395 tests
Form: (WITH-OPEN-FILE (COPY S) (STREAMP COPY))
CORRECT: T
CLISP : ERROR
OS-FILE-ERROR(13): Permission denied
OUT:
"[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied
"
47 weakhash2: 1 error out of 47 tests
Form: (GETHASH "foo" TAB)
CORRECT: "bar"
CLISP : NIL
Differ at position 0: #\b vs COMMON-LISP-USER::END-OF-SEQUENCE
CORRECT: "bar"
CLISP : NIL
...
WARNING: SYSTEM::ENSURE-IMPNOTES-MAP: invalid symbol "POSIX:CLIPBOARD" with id
"clipboard":
READ from #<INPUT STRING-INPUT-STREAM>: #<PACKAGE POSIX> has no
external symbol with name "CLIPBOARD"
662 IDs
"http://clisp.org/beta/impnotes/"
Bye.
make[1]: Target 'check' not remade because of errors
2849411 build-porting64-gcc-heapcodes/cbcstep3.log
I don't see any indications of error but it still ends with
...
WARNING: SYSTEM::ENSURE-IMPNOTES-MAP: invalid symbol "POSIX:CLIPBOARD" with id
"clipboard":
READ from #<INPUT STRING-INPUT-STREAM>: #<PACKAGE POSIX> has no
external symbol with name "CLIPBOARD"
662 IDs
"http://clisp.org/beta/impnotes/"
Bye.
make[1]: Target 'check' not remade because of errors.
2753845 build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log
same as last one
2231568 build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log
same as last one
1615 build-porting64-gcc-multithread_gc/cbcstep3.log
/home/don/hg/clisp/build-porting64-gcc-multithread_gc/clisp: /home/don/hg/clisp/build-porting64-gcc-multithread_gc/base/lisp.run: No such file or directory
Makefile:19: recipe for target 'run-all.fas' failed
1551 build-porting64-gcc-old_gc/cbcstep3.log
same as above (no lisp.run file)
3223709 build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log
see heapcodes - no errors that I see but still ends claiming there are some
4760933 build-porting64-gcc-portability/cbcstep3.log
see below - streams
1559 build-porting64-gcc-safety0/cbcstep3.log
no lisp.run
1639 build-porting64-gcc-safety0-optimized/cbcstep3.log
no lisp.run
1559 build-porting64-gcc-safety3/cbcstep3.log
no lisp.run
1631 build-porting64-gcc-spvw_pure_blocks/cbcstep3.log
no lisp.run
4771802 build-porting64-gcc-typecodes-spvw_mixed_blocks/cbcstep3.log
see below - streams, socket
3363001 build-porting64-gcc-typecodes-spvw_pages/cbcstep3.log
see heapcodes - no errors that I see but still ends claiming there are some
I have the impression that the existence of these files is interpreted
as tests failing, even then they have size zero:
$ ls -l build-*/tests/*.erg
-rw-r--r--. 1 don don 174 Mar 19 08:33 build-porting64-gcc-generic64_heapcodes/tests/streams.erg
-rw-r--r--. 1 don don 147 Mar 19 08:33 build-porting64-gcc-generic64_heapcodes/tests/weakhash2.erg
-rw-r--r--. 1 don don 0 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/tests/characters.erg
-rw-r--r--. 1 don don 0 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/tests/clos.erg
-rw-r--r--. 1 don don 0 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/tests/defhash.erg
-rw-r--r--. 1 don don 0 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/tests/encoding.erg
-rw-r--r--. 1 don don 0 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/tests/eval20.erg
-rw-r--r--. 1 don don 0 Mar 19 08:36 build-porting64-gcc-heapcodes-spvw_pages/tests/characters.erg
-rw-r--r--. 1 don don 0 Mar 19 08:36 build-porting64-gcc-heapcodes-spvw_pages/tests/encoding.erg
-rw-r--r--. 1 don don 0 Mar 19 08:36 build-porting64-gcc-heapcodes-spvw_pages/tests/number.erg
-rw-r--r--. 1 don don 0 Mar 19 08:26 build-porting64-gcc-heapcodes/tests/characters.erg
-rw-r--r--. 1 don don 0 Mar 19 08:26 build-porting64-gcc-heapcodes/tests/encoding.erg
-rw-r--r--. 1 don don 0 Mar 19 08:26 build-porting64-gcc-heapcodes/tests/mop.erg
-rw-r--r--. 1 don don 0 Mar 19 08:26 build-porting64-gcc-heapcodes/tests/number2.erg
-rw-r--r--. 1 don don 0 Mar 19 08:26 build-porting64-gcc-heapcodes/tests/number.erg
-rw-r--r--. 1 don don 0 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/tests/characters.erg
-rw-r--r--. 1 don don 0 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/tests/encoding.erg
-rw-r--r--. 1 don don 0 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/tests/mop.erg
-rw-r--r--. 1 don don 0 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/tests/number2.erg
-rw-r--r--. 1 don don 0 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/tests/number.erg
-rw-r--r--. 1 don don 174 Mar 19 08:21 build-porting64-gcc-portability/tests/streams.erg
-rw-r--r--. 1 don don 848 Mar 19 08:46 build-porting64-gcc-typecodes-spvw_mixed_blocks/tests/socket.erg
-rw-r--r--. 1 don don 174 Mar 19 08:46 build-porting64-gcc-typecodes-spvw_mixed_blocks/tests/streams.erg
-rw-r--r--. 1 don don 0 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/tests/characters.erg
-rw-r--r--. 1 don don 0 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/tests/clos.erg
-rw-r--r--. 1 don don 0 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/tests/encoding.erg
-rw-r--r--. 1 don don 0 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/tests/hashlong.erg
|
|
From: Bruno H. <br...@cl...> - 2017-03-19 17:05:25
|
Don Cohen wrote: > I now try creating a new version of Makefile.devel containing > MULTIBUILD_OPTIONS = --with-threads=POSIX_THREADS > > I hope you see some useful pattern in the following output: > > $ ls -l build-*/cbcstep3.log > -rw-rw-r--. 1 don don 1743 Mar 19 08:52 build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log > -rw-rw-r--. 1 don don 1679 Mar 19 08:51 build-porting64-gcc-generational_gc-old_gc/cbcstep3.log > -rw-rw-r--. 1 don don 4766685 Mar 19 08:33 build-porting64-gcc-generic64_heapcodes/cbcstep3.log > -rw-rw-r--. 1 don don 2849411 Mar 19 08:26 build-porting64-gcc-heapcodes/cbcstep3.log > -rw-rw-r--. 1 don don 2753845 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log > -rw-rw-r--. 1 don don 2231568 Mar 19 08:36 build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log > -rw-rw-r--. 1 don don 1615 Mar 19 08:50 build-porting64-gcc-multithread_gc/cbcstep3.log > -rw-rw-r--. 1 don don 1551 Mar 19 08:49 build-porting64-gcc-old_gc/cbcstep3.log > -rw-rw-r--. 1 don don 3223709 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log > -rw-rw-r--. 1 don don 4760933 Mar 19 08:22 build-porting64-gcc-portability/cbcstep3.log > -rw-rw-r--. 1 don don 1559 Mar 19 08:53 build-porting64-gcc-safety0/cbcstep3.log > -rw-rw-r--. 1 don don 1639 Mar 19 08:54 build-porting64-gcc-safety0-optimized/cbcstep3.log > -rw-rw-r--. 1 don don 1559 Mar 19 08:23 build-porting64-gcc-safety3/cbcstep3.log > -rw-rw-r--. 1 don don 1631 Mar 19 08:48 build-porting64-gcc-spvw_pure_blocks/cbcstep3.log > -rw-rw-r--. 1 don don 4771802 Mar 19 08:47 build-porting64-gcc-typecodes-spvw_mixed_blocks/cbcstep3.log > -rw-rw-r--. 1 don don 3363001 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/cbcstep3.log I can't spot the pattern, no. It would be good to extract a one-line summary of each such log file (OK vs. KO with error message). Bruno |
|
From: <don...@is...> - 2017-03-19 15:59:10
|
Bruno Haible writes: > 2.+4. I added an option --enable-portability that, among other things, > - Enables the most conservative memory model (-DNO_ADDRESS_SPACE_ASSUMPTIONS). > On 32-bit platforms this is the WIDE_SOFT model, on 64-bit platforms it is > ONE_FREE_BIT_HEAPCODES with SPVW_PAGES (and thus no generational GC). > - Disables generational GC, > - Disables all use of ari*.d assembly language files (-DNO_ARI_ASM). I just tried adding that to my mt build - seems to have worked ! I'm pleased to now be able to successfully build at least ONE mt image. I now try creating a new version of Makefile.devel containing MULTIBUILD_OPTIONS = --with-threads=POSIX_THREADS I hope you see some useful pattern in the following output: $ ls -l build-*/cbcstep3.log -rw-rw-r--. 1 don don 1743 Mar 19 08:52 build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log -rw-rw-r--. 1 don don 1679 Mar 19 08:51 build-porting64-gcc-generational_gc-old_gc/cbcstep3.log -rw-rw-r--. 1 don don 4766685 Mar 19 08:33 build-porting64-gcc-generic64_heapcodes/cbcstep3.log -rw-rw-r--. 1 don don 2849411 Mar 19 08:26 build-porting64-gcc-heapcodes/cbcstep3.log -rw-rw-r--. 1 don don 2753845 Mar 19 08:43 build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log -rw-rw-r--. 1 don don 2231568 Mar 19 08:36 build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log -rw-rw-r--. 1 don don 1615 Mar 19 08:50 build-porting64-gcc-multithread_gc/cbcstep3.log -rw-rw-r--. 1 don don 1551 Mar 19 08:49 build-porting64-gcc-old_gc/cbcstep3.log -rw-rw-r--. 1 don don 3223709 Mar 19 08:29 build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log -rw-rw-r--. 1 don don 4760933 Mar 19 08:22 build-porting64-gcc-portability/cbcstep3.log -rw-rw-r--. 1 don don 1559 Mar 19 08:53 build-porting64-gcc-safety0/cbcstep3.log -rw-rw-r--. 1 don don 1639 Mar 19 08:54 build-porting64-gcc-safety0-optimized/cbcstep3.log -rw-rw-r--. 1 don don 1559 Mar 19 08:23 build-porting64-gcc-safety3/cbcstep3.log -rw-rw-r--. 1 don don 1631 Mar 19 08:48 build-porting64-gcc-spvw_pure_blocks/cbcstep3.log -rw-rw-r--. 1 don don 4771802 Mar 19 08:47 build-porting64-gcc-typecodes-spvw_mixed_blocks/cbcstep3.log -rw-rw-r--. 1 don don 3363001 Mar 19 08:40 build-porting64-gcc-typecodes-spvw_pages/cbcstep3.log |
|
From: Bruno H. <br...@cl...> - 2017-03-19 10:43:48
|
Hi Reini, > 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows). > ... > https://github.com/rurban/clisp/commit/7b64a9b41d74460dc361e117700eee9713601ea0 Can you make the builds work on a machine that has not only MSVC but also Cygwin installed? I'm asking because nowadays my preferred way to produce native Windows binaries is by using Cygwin as a development environment, see [1], as it - does not require to manually maintain a config.h (since it's fully autoconfiguring), - does not require the complexity in makemake.in regarding backslashes vs. slashes (since the build relies on GNU make, not nmake), - does not require to regularly update win32msvc/makefile.msvc* (the last update was in 2010!) In other words, is much much simpler. But it requires Cygwin tools. Or in the future, the Microsoft WSL [2] may be reliable enough for this task as well. Bruno [1] http://git.savannah.gnu.org/gitweb/?p=libsigsegv.git;a=blob;f=README.windows [2] https://msdn.microsoft.com/en-us/commandline/wsl/about |
|
From: Bruno H. <br...@cl...> - 2017-03-19 10:31:38
|
Hi Reini, > https://github.com/rurban/clisp/commits/ci > https://travis-ci.org/rurban/clisp/ > https://ci.appveyor.com/project/rurban/clisp/history One of your builds [1], on Linux shows the warning Warning: reserving address range 0x2b0000000000...0x2bffffffffff that contains memory mappings. clisp might crash later! followed by a memory dump. I'm putting this in my TODO list. Bruno [1] https://travis-ci.org/rurban/clisp/jobs/212644808 |
|
From: Bruno H. <br...@cl...> - 2017-03-19 10:25:54
|
Hi,
The first thing many people see from clisp are build failures.
Two months ago, I tried to list the causes of these build failures:
1. GC-safety bugs
2. address range layout and MAP_FIXED
3. C compiler miscompiles something (e.g. Solaris cc)
4. Assembler, can be turned off by -DNO_ASM (= -DSAFETY=3) - but ari80386.d
still makes trouble (e.g. Solaris x86 with cc)
5. Use of rarely used C interfaces, like <asm/page.h> and such.
6. #if-ology that are not tested by Makefile.devel's multibuild.
Here's what has been done about them and can be done in the future.
1. We have a reliable way to detect GC-safety bugs:
build with CC=g++ and --debug-gcsafety, then run "make check".
But this relies of good test coverage in the test suite.
New GC-safety bugs occasionally crop in again. That's life. But it is
helpful if continuous integration builds would catch and signal them soon.
2.+4. I added an option --enable-portability that, among other things,
- Enables the most conservative memory model (-DNO_ADDRESS_SPACE_ASSUMPTIONS).
On 32-bit platforms this is the WIDE_SOFT model, on 64-bit platforms it is
ONE_FREE_BIT_HEAPCODES with SPVW_PAGES (and thus no generational GC).
- Disables generational GC,
- Disables all use of ari*.d assembly language files (-DNO_ARI_ASM).
3. Solaris cc is unusable, both on SPARC and x86/x86_64. Any better idea than
to document in unix/PLATFORMS to avoid it?
5. In general, gnulib is the way to go, in order to avoid the maintenance
effort of using rarely used C interfaces. I think we're using it well,
nothing more to do here.
6. There are now 'multibuild-*' targets in Makefile.devel. But it's only in
combination with continuous integration that they provide their full
benefits.
Bruno
|
|
From: Bruno H. <br...@cl...> - 2017-03-19 10:08:49
|
Hi Reini, Great to hear from you again! > 2. Some minor files have still german comments. I started translating them to english as before. > Progress is in my translate branch. > https://github.com/rurban/clisp/commits/translate > > Will send a patch when ready. There’s also some minor stuff. This is very welcome! > 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows). > This smokes every update, branches and pull requests on these 3 platforms. > It also would allow automatic deployment for binary packages (deb, rpm, windows) at bintray. That’s what we do with the pony compiler. > > https://github.com/rurban/clisp/commits/ci > https://travis-ci.org/rurban/clisp/ > https://ci.appveyor.com/project/rurban/clisp/history > > I’m still tuning the setup a bit, so far only linux runs through. This is also very welcome! Note that Don Cohen is also doing continuous integration builds, but probably with a different approach (on his own machines, as far as I understood) and maybe with a different focus. > So far it’s under my account. I would be happy to transfer it to bruno or sam, if wanted. As long as you manage it, I don't want to steal it from you. I have enough work with the occasional build on other platforms (from FreeBSD to Solaris). Bruno |
|
From: Reini U. <rei...@gm...> - 2017-03-19 09:42:47
|
Hi I subscribed under my latest email address, the older ones died several years ago. I resurrected some old efforts and added some new: 1. I added a github mirror from the hg repo, with bi-hourly updates. https://github.com/rurban/clisp/ I put my branches there. 2. Some minor files have still german comments. I started translating them to english as before. Progress is in my translate branch. https://github.com/rurban/clisp/commits/translate Will send a patch when ready. There’s also some minor stuff. 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows). This smokes every update, branches and pull requests on these 3 platforms. It also would allow automatic deployment for binary packages (deb, rpm, windows) at bintray. That’s what we do with the pony compiler. https://github.com/rurban/clisp/commits/ci https://travis-ci.org/rurban/clisp/ https://ci.appveyor.com/project/rurban/clisp/history I’m still tuning the setup a bit, so far only linux runs through. So far it’s under my account. I would be happy to transfer it to bruno or sam, if wanted. They integrate nicely with github, no idea about sourceforge. Reini Urban |
|
From: Compro P. <com...@gm...> - 2017-03-19 05:32:04
|
"../configure --with-threads=POSIX_THREADS" ran successfully. But "make" stopped after compiling lisp.run Output: rm -rf data mkdir data cd data && ln -s ../../utils/unicode/UnicodeDataFull.txt . cd data && ln -s ../../doc/Symbol-Table.text . gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -Wno-shift-negative-value -O -fwrapv -pthread -fno-strict-aliasing -DENABLE_UNICODE -DMULTITHREAD -DPOSIX_THREADS -DDYNAMIC_FFI -DDYNAMIC_MODULES -Wl,--export-dynamic spvw.o spvwtabf.o spvwtabs.o spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o funarg.o array.o hashtabl.o list.o package.o record.o weak.o sequence.o charstrg.o debug.o error.o misc.o time.o predtype.o symbol.o lisparit.o i18n.o foreign.o unixaux.o zthread.o built.o modules.o libgnu.a -lreadline -lncurses -ldl /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a -lsigsegv -o lisp.run ./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW -lp ../src/ -x '(and (load "../src/init.lisp") (sys::%saveinitmem) (ext::exit)) (ext::exit t)' make: *** [Makefile:1428: interpreted.mem] Segmentation fault (core dumped) Running "./lisp.run" too causes SIGSEGV in this case |
|
From: Bruno H. <br...@cl...> - 2017-03-19 02:01:09
|
Sam,
> This is wrong.
> exec images work on all platforms.
"make check-exec-image" fails at least on OpenBSD/i386, OpenBSD/x86_64, and
MirBSD.
And probably on Cygwin as well, otherwise Ken Brown would not have added
this patch to the Cygwin port of clisp:
# HG changeset patch
# User Ken Brown <kb...@co...>
# Date 1429042817 14400
# Tue Apr 14 16:20:17 2015 -0400
# Node ID 5383b0dea9eef525202949979d621e9f84a91fec
# Parent abc756d38a96bd7959869ca47d66590df7c19baf
Don't allow saving executable memory images on Cygwin
diff -r abc756d38a96 -r 5383b0dea9ee src/savemem.lisp
--- a/src/savemem.lisp Sat Mar 14 14:45:32 2015 -0400
+++ b/src/savemem.lisp Tue Apr 14 16:20:17 2015 -0400
@@ -38,6 +38,9 @@
((:script *script*) (null init-function))
keep-global-handlers (start-package *package*)
(locked-packages *system-package-list*) executable)
+ (if executable
+ (error
+ "Sorry, this build does not support saving executable memory images"))
(let* ((old-driver *driver*) old-global-handlers file-size
(*package* (sys::%find-package start-package))
(active-restarts *active-restarts*)
Bruno
|
|
From: Sam S. <sd...@gn...> - 2017-03-19 01:28:21
|
This is wrong. exec images work on all platforms. On Fri, Mar 17, 2017 at 6:16 PM, Bruno Haible <br...@cl...> wrote: > On 2017-03-13 I wrote: >> But what I need is that "make check" does not abort prematurely, because >> a "make check" failure means - to everyone - "the package is broken, you >> should better not proceed with 'make install'". > > This is now done. If you want to run checks that include unportable ones, > and you are prepared to deal with failures, run > > make check extracheck > > Bruno > -- Sam Steingold <http://sds.podval.org> <http://www.childpsy.net> <http://steingoldpsychology.com> |
|
From: Daniel J. <dan...@gm...> - 2017-03-18 21:30:07
|
Which compiler version are you using? Did you upgrade it recently? Does it also crash when compiled without optimisations (-O0) ? Bruno Haible <br...@cl...> schrieb am Sa., 18. März 2017, 22:04: > Hi Don, > > > Could this be related to the MT problems? > > I was thinking that possibly the failure in MT might be due to > > choosing a different memory model than the one that was working > > before, and that we might find out more by extending your memory > > model test to try to build and run MT versions. > > For me, it crashes even without MT, and in different memory models: > > Linux/x86_64: > build-porting64-gcc-spvw_pure_blocks *** - APPLY: Too > few arguments for #<STANDARD-GENERIC-FUNCTION COMPUTE-SLOTS> > > Linux/arm: > build-porting32-gcc-spvw_pure_blocks/cbcstep3.log KO > Segmentation fault during streams tests > > FreeBSD/i386: > build-porting32-gcc-wide/cbcstep3.log KO > Signal 11 > > FreeBSD/x86_64: > build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log Crash in > steele7 tests > build-porting64-gcc-generational_gc-old_gc/cbcstep3.log Crash in > socket tests > build-porting64-gcc-safety0/cbcstep3.log Crash in > steele7 tests > build-porting64-gcc-safety0-optimized/cbcstep3.log Crash in > steele7 tests > > NetBSD/x86_64: > build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log > Segmentation fault during path tests > > OpenBSD/x86_64: > build-porting64-gcc-heapcodes/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log KO > Segmentation fault during number tests > build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log KO > Segmentation fault during number tests > > 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 > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clisp-devel > |
|
From: Bruno H. <br...@cl...> - 2017-03-18 21:04:39
|
Hi Don, > Could this be related to the MT problems? > I was thinking that possibly the failure in MT might be due to > choosing a different memory model than the one that was working > before, and that we might find out more by extending your memory > model test to try to build and run MT versions. For me, it crashes even without MT, and in different memory models: Linux/x86_64: build-porting64-gcc-spvw_pure_blocks *** - APPLY: Too few arguments for #<STANDARD-GENERIC-FUNCTION COMPUTE-SLOTS> Linux/arm: build-porting32-gcc-spvw_pure_blocks/cbcstep3.log KO Segmentation fault during streams tests FreeBSD/i386: build-porting32-gcc-wide/cbcstep3.log KO Signal 11 FreeBSD/x86_64: build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log Crash in steele7 tests build-porting64-gcc-generational_gc-old_gc/cbcstep3.log Crash in socket tests build-porting64-gcc-safety0/cbcstep3.log Crash in steele7 tests build-porting64-gcc-safety0-optimized/cbcstep3.log Crash in steele7 tests NetBSD/x86_64: build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log Segmentation fault during path tests OpenBSD/x86_64: build-porting64-gcc-heapcodes/cbcstep3.log KO Segmentation fault during number tests build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log KO Segmentation fault during number tests build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log KO Segmentation fault during number tests build-porting64-gcc-one_free_bit_heapcodes/cbcstep3.log KO Segmentation fault during number tests Bruno |
|
From: <don...@is...> - 2017-03-18 19:58:17
|
Could this be related to the MT problems? I was thinking that possibly the failure in MT might be due to choosing a different memory model than the one that was working before, and that we might find out more by extending your memory model test to try to build and run MT versions. Bruno Haible writes: > Hi, > > > i have the same problem as Blake (12.3.2017), with gcc and clang after > > make check. > > > > *** - handle_fault error2 ! address = 0xb00000050b9 not in > > [0xb0000000000,0xb0000001098) ! > > I'm seeing this as well, and not only on Linux/x86_64. > > It's not a "classical" GC-safety bug: the DEBUG_GCSAFETY build does not > flag any violation of the GC-safety rules. > > We will need additional tooling in order to track down this one. > I have some ideas (valdgrind, gcc -fsanitize, and others). > If you have other ideas how to isolate this kind of bug, please speak up! > > Bruno |
|
From: Karsten P. <Kar...@gm...> - 2017-03-18 19:56:11
|
On 18.03.17 19:16, Compro Prasad wrote:
> As I mentioned that non MT build was going well. So, I had already
> installed libsigsegv, libffcall, libreadline and libiconv at the first
> place.
> But when I compiled with MT support using
> ../configure --with-threads=FLAVOUR
> (This time I made the build directory)
FLAVOUR is supposed to be substituted by one of the following:
--with-threads=FLAVOR support multiple threads in one CLISP image
via OS threads [highly experimental - use at your own
risk]
FLAVOR: POSIX_THREADS SOLARIS_THREADS WIN32_THREADS
So either POSIX_THREADS or SOLARIS_THREADS or WIN32_THREADS
regards
Karsten
|
|
From: Bruno H. <br...@cl...> - 2017-03-18 19:49:34
|
Hi, > i have the same problem as Blake (12.3.2017), with gcc and clang after > make check. > > *** - handle_fault error2 ! address = 0xb00000050b9 not in > [0xb0000000000,0xb0000001098) ! I'm seeing this as well, and not only on Linux/x86_64. It's not a "classical" GC-safety bug: the DEBUG_GCSAFETY build does not flag any violation of the GC-safety rules. We will need additional tooling in order to track down this one. I have some ideas (valdgrind, gcc -fsanitize, and others). If you have other ideas how to isolate this kind of bug, please speak up! Bruno |
|
From: Compro P. <com...@gm...> - 2017-03-18 18:16:44
|
As I mentioned that non MT build was going well. So, I had already installed libsigsegv, libffcall, libreadline and libiconv at the first place. But when I compiled with MT support using ../configure --with-threads=FLAVOUR (This time I made the build directory) I got the output posted at http://paste.lisp.org/display/341721 which I think is error free. The problem arises when I use make. It gives a long output hosted at two locations http://paste.lisp.org/display/341722 and http://paste.lisp.org/display/341723 . According to me it was missing libpthread, so the next time I ran make CFLAGS+="-lpthread" which did work for most of the part when it suddenly broke with the message: *** - SYSTEM::%FIND-PACKAGE: There is no package with name "FFI" Since, it was too long so it took three pages: http://paste.lisp.org/display/341724 http://paste.lisp.org/display/341725 http://paste.lisp.org/display/341726 My system: uname -rom: 4.10.2-1-ARCH x86_64 GNU/Linux gcc --version: gcc (GCC) 6.3.1 20170306 make --version: GNU Make 4.2.1 libffcall 1.10 libreadline 7.0 libiconv 1.15 libsigsegv 2.10 On Sat, Mar 18, 2017 at 7:38 PM, Bruno Haible <br...@cl...> wrote: > Hi Prasad, > > > But when using "./configure --with-threads=flavour" > > Parts of commands that need to be substituted by actual values are > highlighted > in a particular way: > - in HTML documentation: through italics, > - in "configure --help" output: through uppercase. > > > It complains about not > > having package FFI. For further information I have given the output of > > `make CFLAGS+="-lpthread"` below which I have ran from the project root: > > > > cd src && /usr/bin/make all > > make[1]: Entering directory > > '/run/media/compro/eb7b593c-d20e-4393-be34-3b108921f50e/ > home/compro/Dropbox/programs/hg/clisp/src' > > ./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW > > -M halfcompiled.mem -q -c foreign1.lisp -o ./ > > ;; Compiling file > > /run/media/compro/eb7b593c-d20e-4393-be34-3b108921f50e/ > home/compro/Dropbox/programs/hg/clisp/src/foreign1.lisp > > ... > > *** - SYSTEM::%FIND-PACKAGE: There is no package with name "FFI" > > Most probably you have reused a build directory for re-configuring with > different configure options. This does not work. Always run "../configure > ...." > in a fresh (empty) subdirectory of the clisp top directory. > > If you actually want to build with FFI, you need to first install > libffcall. > https://www.gnu.org/software/libffcall/ > > Bruno > > |
|
From: <don...@is...> - 2017-03-18 14:27:29
|
> if this is a regression, you might want to try 'hg bisect' to pinpoint > the commit which broke MT. I think it's a little more complicated than that. Both my MT and non-MT builds stopped working at the same time. latest changes break build From: <don-sourceforge-x2012@is...> - 2017-02-27 14:24:38 Then a bunch of changes later, the non-MT builds started working again. progress in nightly builds From: <don-sourceforge-x2012@is...> - 2017-03-10 14:52:21 |
32 messages has been excluded from this view by a project administrator.
