Opened 15 years ago

Closed 15 years ago

#4713 closed defect (fixed)

clisp fails to build

Reported by: iqgrande Owned by: gwright@…
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc: darwinports-bugs@…
Port:

Description

Hello. Clisp fails to build. The output of

make --version gcc --version

is below. I am running Mac OS X 10.4.2 with Xcode 2.1 with X11, X11SDK, and gcc33 installed (from the Developer Tools). The following 2 outputs I sent to the maintainer, gwright@… (too long to append to this, and I do not have sufficient knowledge to know what to dismiss).

sudo port clean --all clisp sudo port -dv install clisp > build.log 2>&1

tibook:~ iqgrande$ make --version GNU Make 3.80 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. tibook:~ iqgrande$ gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Attachments (2)

build.log (99.8 KB) - added by iqgrande 15 years ago.
build.log
clisp_bld.log (91.2 KB) - added by coomes@… 15 years ago.
output from "sudo port -d install clisp"

Download all attachments as: .zip

Change History (15)

Changed 15 years ago by iqgrande

Attachment: build.log added

build.log

comment:1 Changed 15 years ago by gwright@…

Status: newassigned

Thanks for sending this.

We have the same versions of make and gcc, so that appears not to be the problem.

-Greg

comment:2 Changed 15 years ago by gwright@…

Anthony,

What's you hardware platform? It appears that the trouble is in the low-level machine dependent code.

It may be that clisp just won't work for you; I don't think it is well tested on other than G4 machines. Would an +openmcl variant for maxima suffice? You wouldn't be able to use TeXmacs as a front end, but everything else should work.

-Greg

comment:3 Changed 15 years ago by gwright@…

Anthony,

We also have the same gcc and make, so that's not the problem.

-greg

comment:4 Changed 15 years ago by gwright@…

Anthony,

There is a possibility that your clisp problem is an upstream bug. My machine, essentially identical in software, uses a PPC 745x processor. The 400 MHz Ti Books used a PPC 7410, I believe. I wonder if the assembly code bits of clisp have changed and are no longer compatible with your machine.

-Greg

comment:5 Changed 15 years ago by gwright@…

Anthony,

A suggestion: try setting

gcc_select 3.3

and cleaning and building:

sudo port clean --all clisp sudo port -dv build clisp > build.log 2>&1

It may be that the gcc 4.0 generate bad code for your machine.

-Greg

comment:6 Changed 15 years ago by gwright@…

I have committed an version bump to 2.35. If I don't hear otherwise, I'll assume this bug is fixed and can be closed.

-Greg

comment:7 Changed 15 years ago by gwright@…

Resolution: fixed
Status: assignedclosed

Since we're now on 2.35 and no one has spoken up about this problem, I am closing this bug.

-Greg

Changed 15 years ago by coomes@…

Attachment: clisp_bld.log added

output from "sudo port -d install clisp"

comment:8 Changed 15 years ago by gwright@…

Resolution: fixed
Status: closedreopened

Anthony,

You might try "sudo port selfupdate" followed by "sudo port clean --all clisp" and "sudo port -dv install clisp 2>&1 build.log".

There have been changes to the DP system to pass only a very limited set of shell variable to the environment of the build process. It's possible that something in your environment is causing the build to fail, which a newer DP will fix.

Clisp-2.35 builds fine for me with no errors on by G4 AlBook 1.5 GHz, 1 GB RAM, OS X 10.4.2.

-Greg

comment:9 Changed 15 years ago by tadpol@…

clisp didn't build for me either. I changed two lines to the portfile, and then it built fine.

In the post-configure, I added "--fsstnd=netbsd" and changed "--with-dynamic-ffi" to "--without- dynamic-ffi"

with those changes, it works fine for me.

comment:10 Changed 15 years ago by gwright@…

Michael,

Was the --fsstnd=netbsd necessary or would just --without-dynamic-ffi do? I'll add a noffi variant to cover people who find that the ffi won't build for them, but I'm not sure about the --fsstnd=netbsd.

Greg

(In reply to comment #11)

clisp didn't build for me either. I changed two lines to the portfile, and

then it built fine.

In the post-configure, I added "--fsstnd=netbsd" and changed

"--with-dynamic-ffi" to "--without-

dynamic-ffi"

with those changes, it works fine for me.

comment:11 Changed 15 years ago by tadpol@…

(In reply to comment #12)

Was the --fsstnd=netbsd necessary or would just --without-dynamic-ffi do?

--without-dynamic-ffi is all that is really needed.

comment:12 Changed 15 years ago by gwright@…

In the 2.37 portfile, the dynamic ffi is disabled by default. To turn it on, use the +dynffi variant. This should resolve the problem reported here. Let me know if it works.

-Greg

comment:13 Changed 15 years ago by gwright@…

Resolution: fixed
Status: reopenedclosed

Hi,

I'm going to close this bug out, since the new 2.37 portifle seems to have all of the options needed to build on both Panther and TIger. Building without the dynamic ffi by default also seems to have fixed some previously failing builds.

If something fails in the future, a new bug report can be opened.

-Greg

Note: See TracTickets for help on using tickets.