From: SourceForge.net <no...@so...> - 2010-07-20 21:44:13
|
Bugs item #3026922, was opened at 2010-07-08 12:08 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3026922&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: ANSI compliance issue >Status: Pending >Resolution: Invalid Priority: 5 Private: No Submitted By: Sergei (sergeiste) Assigned to: Sam Steingold (sds) Summary: clisp-2.49 breaks sbcl build; clisp-2.48 was OK Initial Comment: I've been routinely building SBCL since its version 1.0.37 using clisp-2.48 for bootstrapping. At the moment the latest SBCL successfully built with clisp-2.48 is sbcl-1.0.40. Using clisp-2.49 built with exactly the same libraries as clisp-2.48 breaks sbcl-1.0.40 build. I am not a lisp guy and I do not know whether SBCL uses something illegal/deprecated from CLISP, but the breakage is a fact. I am about to upload SBCL 'make' scree output showing the problem. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-07-20 17:44 Message: This bug report is now marked as "pending"/"invalid". This means that we think that the problem you report is not a problem with CLISP. Unless you - the reporter - act within 2 weeks, the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2010-07-08 14:30 Message: Thanks for the clarifications. I've filed https://bugs.launchpad.net/sbcl/+bug/603286 - I hope that SBCL developers will agree with CLISP developers and adjust the build system. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-07-08 14:28 Message: This bug report is now marked as "pending"/"invalid". This means that we think that the problem you report is not a problem with CLISP. Unless you - the reporter - act within 2 weeks, the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-07-08 13:55 Message: note that your "config_wrapper.sh" passes --with-module=regexp --with-module=syscalls --with-module=i18n --with-module=readline to clisp configure. this is wrong: these are base modules, they are always included. http://clisp.cons.org/impnotes/faq.html#faq-modules http://clisp.cons.org/impnotes/modules.html#base-modules ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-07-08 13:38 Message: the problem is that clisp now uses CLCS for compilation diagnostics and redefinition warnings now count as compilation warnings and the SBCL build process thinks that compilation failed. workarounds: either set custom:*suppress-check-redefinition* to nil or tell the SBCL compilation system to ignore warnings. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3026922&group_id=1355 |