clisp fails to complete installation due to readline dependency problem

[0x6d65@…]

Overview Description: Using the command:

sudo port install clisp

fails in the building step of installation due to a readline dependency. I have the most recent version of readline I can get, but the installation seems to want a later one?

Steps to Reproduce: On a machine running Tiger (OS 10.4.2), at home directory, type

sudo port install clisp

The installation should fail during the install step.

Actual Results: Installation died without installing a working clisp. I've appended the output from trying to install and from a few other commands.

Expected Results: A working clisp implementation.

Build and platform: clisp 2.33.2 (most recent as of 26 July 2005) on OS X Tiger (10.4.2)

[0x6d65@…]

Output from trying to install clisp

[gwright@…]

HI Shawn,

This is very odd. I rebult clisp using the new trace option (which searches for dependencies by tracking the system calls that link the libraries). It indicated no missing dependency on readline. Indeed, readline is a dependency in the port file.

It looks as if you are getting a different readline (e.g., /usr/lib/libreadline.dylib). I will modify the portfile to search for the readline port and see what I can do to fix the link order. Unfortunately, clisp using a nonstandard configuration procedure, so it may take a while to figure out.

-Greg

[gwright@…]

I have just made readline a "port" dependency (so DP should check that the port is installed) and added a dependency on gettext. Please give this a try. (EIther update from cvs or run "sudo port selfupdate".) If it still doesn't work, I think I know what the additional problem is and can fix it.

-Greg

[0x6d65@…]

The change didn't resolve the problem. After doing a successful "sudo port selfupdate" and "sudo port clean clisp", the behavior was the same.

[gwright@…]

Shawn,

Could you send the output of

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

as an attachment to the bug? I still can't reproduce the failure you are seeing, and the failure looks as if something has gone wrong with your configuration process. The output of that might shed some light on the problem.

Thanks. Greg

[0x6d65@…]

Output from "sudo port -dv build clisp > build.log 2>&1"

[gwright@…]

Hi Shawn,

The build log reveals what the problem is: on your system, the CPPFLAGS variable is getting clobbered. It should be set by the configuration process to /opt/local/linclude or <DP>/include, if you have DP in a nonstandard location.

Do you set CPPFLAGS in your .profile (or whatever shell startup you use)?

What is the output of

/bin/sh --version

?

I can force the setting of CPPFLAGS in the portfile but I don't want to do that until I understand what the reason for the configuration failure is.

Greg

[gwright@…]

Hi Shawn,

Try running selfupdate again and building clisp using

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

I've set the configuration environment to explicitly pass the CPPFLAGS and LDFLAGS variables.

Let me know if this works. If not, I think there in an environment passing bug in the DP infrastructure.

-Greg

[gwright@…]

Shawn,

Did the latest portfile work for you? I would like to close this bug--I think your problem is not really clisp--and I'll open a new bug report if necessary about the environment variable passing issue.

-Greg

[gwright@…]

Shawn reports that the latest portfile works. The fix seems to be to pass the CPPFLAGS and LDFLAGS variables explicitly in configure.env. This is a bit odd, since on my machine the configuration procedure correctly sets these variables.

It may be just configure script fragility (no surprise there), but I'll keep an eye open for any symptoms of environment variables getting clobbered.

-Greg