From: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-user@gnu.org
Subject: Re: Guile-PG 0.91 - what am I doing wrong?
Date: 04 Jun 2004 11:02:54 -0400 [thread overview]
Message-ID: <rmi8yf31i3l.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87y8n4aj0e.fsf@naia.homelinux.net>
The build went OK, and the install _seemed_ to - turns out (after a
couple of hours of reading manuals, poking around in the system, etc.)
that 'make install' put the libs in '/site' *not*
/usr/local/lib/guile/site, and the scripts in /database *not* in
/usr/local/share/guile/site.
Try 'make check' in the build dir.
OK, fine, let's move them to where they should have been, and update my
GUILE_LOAD_PATH to point to /usr/local/share/guile/site, my
LTDL_LIBRARY_PATH and LD_LIBRARY_PATH to
"/usr/local/pgsql/lib:/usr/local/lib/guile/site". (I also tried with
"/usr/local/lib/guile/site/database" with the same dismal results).
Looking at auto* stuff, it seems the install is trying to put bits in
sensible places but ending up with bad paths, I think because it is
using a ttn-1.4 added config feature. I got the same problems as you
with 0.19.
I just tried 0.16 again, and had to add -R/usr/pkg/lib to
config.status's pq lib line to get rpath in the libpostgres.so
installed by guile-pg. I also has to add (current-module) to the eval
in the lo check script. Then 'make check' worked.
This is with guile 1.6.4 on NetBSD currentish with pg 7.3.4.
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-06-04 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 13:06 Guile-PG 0.91 - what am I doing wrong? Chris Hall
2004-06-04 15:02 ` Greg Troxel [this message]
2004-06-04 19:40 ` Chris Hall
2004-06-06 2:20 ` Chris Hall
2004-07-04 7:53 ` Chris Hall
2004-06-06 3:21 ` Thien-Thi Nguyen
2004-06-06 11:32 ` Chris Hall
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=rmi8yf31i3l.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-user@gnu.org \
/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).