[ clisp-Bugs-3514029 ] clisp does not build on OSX (Macports)

[SourceForge.net <no...@so...>]

Bugs item #3514029, was opened at 2012-04-01 21:40
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3514029&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: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Christopher Stacy (cstacy)
Assigned to: Bruno Haible (haible)
Summary: clisp does not build on OSX (Macports)

Initial Comment:
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.



----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2012-04-24 21:58

Message:
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?

----------------------------------------------------------------------

Comment By: Christopher Stacy (cstacy)
Date: 2012-04-24 18:10

Message:
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.


----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2012-04-24 12:52

Message:
: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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3514029&group_id=1355