unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Pkgsrc patches: patch-ah
Date: Fri, 15 Feb 2008 20:53:25 -0500	[thread overview]
Message-ID: <rmid4qxmzu2.fsf_-_@fnord.ir.bbn.com> (raw)
In-Reply-To: <87ir0r9yrb.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Thu, 14 Feb 2008 19:30:32 +0100")

This one you probably don't want to apply, but I'm sending it to point
out a much larger problem.  Programs that muck with library paths really
need to figure out what the rules are on the local system and deal
appropriately.  On NetBSD one needs -Wl,-R (or just -R really) to point
to the libdir at runtime when linking, not just -L to find the library.
This is not an issue on linux because of the common use of /usr, I think.

There are more serious issues with dynlinking of .so modules, and on
Darwin there are some PRs open about guile and guile-using programs that
I don't yet fully understand.

I think the fix involves a configure test to decide the -R rules, and
then conditional code to behave differently.


$NetBSD: patch-ah,v 1.3 2007/07/20 00:09:23 gdt Exp $

--- guile-config/guile-config.in.orig	2007-05-09 16:22:03.000000000 -0400
+++ guile-config/guile-config.in
@@ -155,7 +155,7 @@
                (if (or (string=? libdir "/usr/lib")
                        (string=? libdir "/usr/lib/"))
 		   ""
-		   (string-append "-L" (get-build-info 'libdir)))
+		   (string-append "-Wl,-R" (get-build-info 'libdir) " -L" (get-build-info 'libdir)))
 	       (string-join other-flags)
 
 	       )))





  parent reply	other threads:[~2008-02-16  1:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 14:18 Honor `$TMPDIR' in `guile-snarf' Ludovic Courtès
2008-02-12 20:53 ` Neil Jerram
2008-02-12 21:28   ` Bruce Korb
2008-02-12 21:52   ` Ludovic Courtès
2008-02-13 20:25   ` Aleksej Saushev
2008-02-14  7:48     ` Thien-Thi Nguyen
2008-02-14 17:54       ` Aleksej Saushev
2008-02-14 18:30         ` Pkgsrc patches Ludovic Courtès
2008-02-15 20:51           ` Greg Troxel
2008-02-16  1:49           ` patches from pkgsrc - patch-aa Greg Troxel
2008-02-16 11:46             ` Ludovic Courtès
2008-02-16  1:50           ` Pkgsrc patches: patch-ae Greg Troxel
2008-02-16 18:49             ` Ludovic Courtès
2008-02-18 17:12               ` Greg Troxel
2008-02-16  1:50           ` Pkgsrc patches: patch-ag Greg Troxel
2008-02-16 19:28             ` Ludovic Courtès
2008-02-18 14:29               ` Greg Troxel
2008-02-18 15:05                 ` Ludovic Courtès
2008-02-18 16:05                   ` Greg Troxel
2008-02-16  1:53           ` Greg Troxel [this message]
2008-02-16  1:55           ` Pkgsrc patches: patch-aj Greg Troxel
2008-02-26 21:58             ` Neil Jerram
2008-02-26 23:41               ` Greg Troxel
2008-02-27 12:20               ` Greg Troxel
2008-02-27 21:27                 ` Neil Jerram
2008-02-16  1:59           ` Pkgsrc patches Greg Troxel

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=rmid4qxmzu2.fsf_-_@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).