unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Roger Mc Murtrie <rogermc@iinet.net.au>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Intel Mac-mini OSX 10.5.1 guile test results
Date: Fri, 25 Jan 2008 00:36:38 +1100	[thread overview]
Message-ID: <4C6B44CC-8612-43D9-BBEB-53FCDB4D1D95@iinet.net.au> (raw)
In-Reply-To: <873asoktvn.fsf@ossau.uklinux.net>

I did as you suggested but make check produced the same result.
As before ./configure failed with a couple of undefined symbols so I  
had build without shared libraries.

As your changes appear to be concerned with dynamic libraries, I  
wonder if building only static libraries has anything to do with the  
problem.
Irrespective, I'll see if I can find those undefined symbols and get  
it to build shared libraries.

Roger

On 24/01/2008, at 10:24 AM, Neil Jerram wrote:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Roger Mc Murtrie <rogermc@iinet.net.au> writes:
>>
>>> make  check-TESTS
>>> PASS: test-system-cmds
>>> ERROR: In procedure dynamic-link:
>>> ERROR: file: "libguile-srfi-srfi-1-v-3", message: "dlopen(libguile-
>>> srfi-srfi-1-v-3.a, 9): image not found"
>>> FAIL: test-require-extension
>>> PASS: test-num2integral
>>> PASS: test-round
>>> PASS: test-gh
>>> ERROR: In procedure dynamic-link:
>>> ERROR: file: "libtest-asmobs", message: "dlopen(libtest-asmobs.a,  
>>> 9):
>>
>> Sounds like this:
>> http://comments.gmane.org/gmane.comp.gnu.libtool.general/8440
>>
>> I need a bit longer to digest what the conclusions are, though!  Will
>> follow up when I've done that.
>
> For the build that was failing with dynamic-link problems (per above),
> can you try patching pre-inst-guile-env.in and pre-inst-guile.in as
> below, and report if that helps?
>
> You may first want to do
>
>    sudo touch /var/db/.AllowDYLDEnvironmentVariables
>
> to make sure that
> http://docs.info.apple.com/article.html?artnum=305509 is not a factor.
>
> (You'll need to make distclean and run the ./configure step again, so
> that pre-inst-guile-env and pre-inst-guile are regenerated from the
> patched .in files.)
>
> Thanks,
>        Neil
>




  reply	other threads:[~2008-01-24 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  3:57 Intel Mac-mini OSX 10.5.1 guile test results Roger Mc Murtrie
2008-01-10 19:08 ` Neil Jerram
2008-01-23 23:24   ` Neil Jerram
2008-01-24 13:36     ` Roger Mc Murtrie [this message]
2008-01-24 22:01       ` Neil Jerram
     [not found]         ` <7A8A3E01-C259-46BB-8FA7-92F75AAB7642@iinet.net.au>
     [not found]           ` <87y7ae3kqj.fsf@ossau.uklinux.net>
2008-01-25  1:31             ` Roger Mc Murtrie
2008-01-25  8:20               ` Roger Mc Murtrie
2008-01-29 23:09                 ` Neil Jerram
2008-01-30  0:35                   ` Roger Mc Murtrie
2008-01-30 21:54                     ` Neil Jerram
     [not found] ` <87zlvept9v.fsf@ossau.uklinux.net>
     [not found]   ` <0CAB0B4F-7CA6-4892-9066-BA9D0CA56EAF@iinet.net.au>
     [not found]     ` <7A68F70F-CCDB-46E7-9B11-D4B564B33F7C@iinet.net.au>
     [not found]       ` <87prw91dwv.fsf@ossau.uklinux.net>
2008-01-10 23:46         ` Roger Mc Murtrie

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=4C6B44CC-8612-43D9-BBEB-53FCDB4D1D95@iinet.net.au \
    --to=rogermc@iinet.net.au \
    --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).