From: Hans Aberg <haberg@math.su.se>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4
Date: Sat, 8 Mar 2008 00:13:11 +0100 [thread overview]
Message-ID: <9B3A957D-B759-4081-8879-18851D88730F@math.su.se> (raw)
In-Reply-To: <87bq5qcgzh.fsf@ossau.uklinux.net>
On 7 Mar 2008, at 23:21, Neil Jerram wrote:
>> Otherwise, a fix might be that the Guile installation checks for
>> readline in /usr/local/.
>
> I could well be wrong, but my current understanding is that that won't
> work, because at link time GCC or ld.so
(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.)
> 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>
Or must some other stuff, like in /usr/include, also be relinked?
Hans Aberg
next prev parent reply other threads:[~2008-03-07 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 18:03 Guile-1.8.4 compile bug Mac OS X 10.4.11 PPC G4 Hans Aberg
2008-02-23 10:13 ` Ludovic Courtès
2008-02-23 18:21 ` Neil Jerram
2008-03-07 19:55 ` Neil Jerram
2008-03-07 21:20 ` Hans Aberg
2008-03-07 22:21 ` Neil Jerram
2008-03-07 23:13 ` Hans Aberg [this message]
2008-03-08 12:19 ` Neil Jerram
2008-03-08 13:48 ` Hans Aberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9B3A957D-B759-4081-8879-18851D88730F@math.su.se \
--to=haberg@math.su.se \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).