#635 clisp does not build on OSX (Macports)

build problems
open
clisp (525)
5
2016-12-11
2012-04-02
No

Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386

System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: No

Model Name: Mac mini
Model Identifier: Macmini3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 8 GB
Bus Speed: 1.07 GHz
SMC Version (system): 1.35f1

There does not seem to be a custom GCC in Macports, so I guess it's using this one:
i686-apple-darwin10-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)

sudo port install clisp
---> Computing dependencies for clisp
---> Building clisp
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for clisp is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_clisp/clisp/main.log
Error: Status 1 encountered during processing.

Discussion

  • Sam Steingold

    Sam Steingold - 2012-04-24

    :info:build ;; Loading file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_clisp/clisp/work/clisp-2.49/src/clos-methcomb2.fas ...
    :info:build *** - (SETF METHOD-COMBINATION-CHECK-OPTIONS): variable NEW-VALUE has no value

    this is extremely weird.
    other log messages indicate that this is not a clean build.
    please try a clean build in a separate directory.

     
  • Christopher Stacy

    Can you be more specific about what makes you think there is contamination?

    I did this sequence:
    port clean clisp
    port uninstall clisp

    Then I verified that the /opt/local/var/macports/build subdirectory for clisp was now gone.

    Then I did:
    port install clisp

    I get the same answer as before (same logs as I originally reported).
    (This is what I did for the original report; I just now did the whole thing over again).

    I have the latest (as of 24-April-2012) "selfupdate" of MacPorts installed.

     
  • Sam Steingold

    Sam Steingold - 2012-04-25

    What I see is that
    - configure is not run
    - gcc is not run
    - compiled (*.fas) files are loaded into the run-time for the initial memory dump.
    the is indicative of a "make" in a pre-existing build directory.

    I don't know what the "port" command does.
    as long as you are reporting the bug in terms of it, I cannot help you.
    could you please take a look at clisp/unix/INSTALL and try to follow the instructions there?

     
  • Christopher Stacy

    "port" is the command that invokes the BSD package management system; it corresponds to "rpm" or "yum" or "apt-get" on Linux distributions. This "port" is MacPorts aka DarwinPorts, which is the version for the Mac.

    It is downloading the source, running configure, doing the make, and install.

    Apparently I am complaining in the wrong place, as the maintainer for the package in this distribution is not here. I will see if I can figure out who is responsible for it.

     
  • Pascal J. Bourguignon

    Perhaps the bug #635 should be closed: current clisp builds on MacOSX, either stand alone or thru MacPort. However, there remain a problem: configure cannot find the ffcall libraries. cf. https://sourceforge.net/p/clisp/bugs/690/

     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks