[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4

From: Hans Aberg
Subject: Re: Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4
Date: Sat, 8 Mar 2008 14:48:39 +0100

On 8 Mar 2008, at 13:19, Neil Jerram wrote:

(On Mac OS X, dynamic libraries end with .dylib, being a Mach-O
format. The .so is for a fromat used on GNU/Linux computers.)

OK, thanks.

For what I have checked, the functions are named the same. So if one assumes the dynamic libraries have been created on Mac OS X, the only change needed in the source code is to look for files ending in .dylib instead of .so.

will always prefer to pick up
-lreadline from /usr/lib rather than from /usr/local/lib.

It could be, because the reason I installed latest readline was that I
wanted Hugs and GHCi working with UTF-8, and it didn't work.

Suppose I set a soft link from the system readline to the newly
installed, would it suffice to set it from
  /usr/lib/libreadline.<ext> -> /usr/local/lib/libreadline.<ext>

Yes, that should work.  Sysadmin-wise, it's a confusing change to keep
track of, though.

Yes, it is a mess. :-)

Or must some other stuff, like in /usr/include, also be relinked?

No, I don't think that will be needed.  As long as you have
CFLAGS=-I/usr/local/include when you run ./configure, I believe that
headers under /usr/local/include will be picked up in preference to
those under /usr/include.

(BTW, this is something that I've never seen a good explanation for.
-I/usr/local/include takes preference over the standard /usr/include,
but -L/usr/local/lib doesn't take preference over the standard
/usr/lib.  What is the logic there?)

It is certainly causing problems. Somebody got problems on the GMP list reported problems with that package and Guile (Mac OS X 10.5 Intel perhaps). But it strikes me now, in view of your letters, that it might be due to the same issue as with readlib.

Do you happen to know with there are any environment variables one might set for GCC, like LIBPATH, INCLUDEPATH, or something, that ensures /usr/local is included? This would be a convenient method.

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]