From: Dan McMahill <mcmahill@mtl.mit.edu>
To: "Ludovic Courtès" <ludo@chbouib.org>, guile-user <guile-user@gnu.org>
Subject: Re: debugging guile test failure and segfault.
Date: Sun, 10 Jun 2007 12:37:18 -0400 [thread overview]
Message-ID: <466C28BE.1090304@mtl.mit.edu> (raw)
In-Reply-To: <878xasvsbh.fsf@chbouib.org>
Ludovic Courtès wrote:
> Hi,
>
> Dan McMahill <mcmahill@mtl.mit.edu> writes:
>
>>>> I'm also working on getting this going on Solaris-2.9/sparc but am not
>>>> quite to the testsuite part. I have a few bug fix patches there
>>>> too. Once I get my various problems worked out, I'll submit a more
>>>> cleaned up set of patches.
>> see the attached file for most of my patches.
>
> [...]
>
>> --- guile-config/guile-config.in.orig 2006-09-20 00:19:02.000000000 +0000
>> +++ 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)
>>
>> )))
>
> Can you explain why this is needed? `guile-config' is only used by
> applications that link against Guile. Did you have troubles compiling
> such applications?
With that I don't have to modify the guile-config output. In other
words by default I might just get "-L/my/guile/path/lib" where I may
actually want "-L/my/guile/path/lib -Wl,-R/my/guile/path/lib".
> Besides, `-Wl,-R' can probably not be considered portable.
which is why one would need a test for it.
Anyway, I figured this one was questionable for general consumption
which is why I kept it apart from the others.
-Dan
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-06-10 16:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 16:49 debugging guile test failure and segfault Dan McMahill
2007-06-06 8:24 ` Ludovic Courtès
2007-06-07 5:09 ` Dan McMahill
2007-06-07 8:57 ` Ludovic Courtès
2007-06-08 22:53 ` Dan McMahill
2007-06-10 13:51 ` Ludovic Courtès
2007-06-10 16:50 ` Dan McMahill
2007-06-11 7:38 ` Ludovic Courtès
2007-06-11 11:49 ` Ludovic Courtès
2007-06-11 21:46 ` Dan McMahill
2007-06-09 14:18 ` Dan McMahill
2007-06-10 13:42 ` Ludovic Courtès
2007-06-10 16:37 ` Dan McMahill [this message]
2007-06-11 21:02 ` Ludovic Courtès
2007-06-12 14:47 ` Greg Troxel
2007-06-12 17:10 ` Ludovic Courtès
2007-06-13 13:05 ` Greg Troxel
2007-06-13 13:07 ` Greg Troxel
2007-06-13 15:08 ` Ludovic Courtès
2007-06-10 17:46 ` Greg Troxel
2007-06-13 9:43 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2007-06-13 16:09 dsmich
2007-06-13 16:16 ` Ludovic Courtès
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=466C28BE.1090304@mtl.mit.edu \
--to=mcmahill@mtl.mit.edu \
--cc=guile-user@gnu.org \
--cc=ludo@chbouib.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).