#557 clisp-2.49 breaks sbcl build; clisp-2.48 was OK

closed-invalid
clisp (525)
5
2010-09-26
2010-07-08
Sergei
No

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.

Discussion

  • Sergei

    Sergei - 2010-07-08

    broken by clisp-2.49 SBCL 'make' screen output

     
    Attachments
  • Sergei

    Sergei - 2010-07-08

    screen output of successfule SBCL build with clisp-2.48

     
    Attachments
  • Sergei

    Sergei - 2010-07-08

    autogenerated 'configure' wrapper used to build clisp-2.49

     
    Attachments
  • Sam Steingold

    Sam Steingold - 2010-07-08
    • assigned_to: haible --> sds
    • milestone: --> ANSI compliance issue
     
  • Sam Steingold

    Sam Steingold - 2010-07-08

    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.

     
  • Sam Steingold

    Sam Steingold - 2010-07-08
    • status: open --> pending-invalid
     
  • Sam Steingold

    Sam Steingold - 2010-07-08

    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.

     
  • Sergei

    Sergei - 2010-07-08
    • status: pending-invalid --> open
     
  • Sergei

    Sergei - 2010-07-08

    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.

     
  • Sam Steingold

    Sam Steingold - 2010-07-20

    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.

     
  • Sam Steingold

    Sam Steingold - 2010-07-20
    • status: open --> pending-invalid
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-invalid --> closed-invalid
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks