From: Tim Meehan <btmeehan@gmail.com>
To: Tim Van den Langenbergh <tmt_vdl@gmx.com>
Cc: guile-user@gnu.org
Subject: Re: dynamic-link sadness
Date: Tue, 23 Feb 2021 08:18:33 -0600 [thread overview]
Message-ID: <ABDEEB3C-3103-46A1-B18C-20292DAB04C4@gmail.com> (raw)
In-Reply-To: <4E0432AB-3BDC-4094-A1F2-A4336D4D29A9@gmail.com>
(It is a bit weird writing to “Tim,” but my last job there were three “Tim”s ... even weirder)
I figured it out. The string argument on my system was the path to a symlink, the actual file was “/usr/lib/x86_64-linux-gnu/libm-2.32.so” so it won’t follow symlinks to load libraries.
> On Feb 23, 2021, at 06:45, Tim Meehan <btmeehan@gmail.com> wrote:
>
> Sorry, I should have said that it was Linux Mint Ulyssa, installed from “apt”. I have another system I can try it on later today.
>
>>> On Feb 23, 2021, at 06:21, Tim Van den Langenbergh <tmt_vdl@gmx.com> wrote:
>>>
>>> On Tuesday, 23 February 2021 04:49:34 CET you wrote:
>>> Ok - I think that I am missing something important that will allow me to
>>> dynamically load libraries. :(
>>> Is this an environment variable or something?
>>>
>>> me@expensive:/usr$ find . -type f -name "libm\.*" -print
>>> ./lib/x86_64-linux-gnu/libm.so
>>> ./lib/x86_64-linux-gnu/libm.a
>>> me@expensive:/usr$ guile
>>> GNU Guile 3.0.1
>>> Copyright (C) 1995-2020 Free Software Foundation, Inc.
>>>
>>> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
>>> This program is free software, and you are welcome to redistribute it
>>> under certain conditions; type `,show c' for details.
>>>
>>> Enter `,help' for help.
>>> scheme@(guile-user)> (dynamic-link "libm")
>>> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
>>> In procedure dynamic-link: file: "libm", message: "file not found"
>>>
>>> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
>>> scheme@(guile-user) [1]> ,q
>>> scheme@(guile-user)> (dynamic-link "/usr/lib/x86_64-linux-gnu/libm.so")
>>> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
>>> In procedure dynamic-link: file: "/usr/lib/x86_64-linux-gnu/libm.so",
>>> message: "file not found"
>>>
>>> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
>>> scheme@(guile-user) [1]> ,q
>>
>> Hey Tim (feels weird typing that),
>>
>> are you using Guile from your Guix install? I have had issues with that as
>> well and I needed to use Guile from my regular OS.
>>
>> If you're not using Guix then I haven't had that problem, so I'm afraid I
>> can't help.
>>
>> Vale,
>>
>> -Tim Van den Langenbergh
>>
>>
prev parent reply other threads:[~2021-02-23 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 3:49 dynamic-link sadness Tim Meehan
2021-02-23 12:21 ` Tim Van den Langenbergh
2021-02-23 12:45 ` Tim Meehan
2021-02-23 14:18 ` Tim Meehan [this message]
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=ABDEEB3C-3103-46A1-B18C-20292DAB04C4@gmail.com \
--to=btmeehan@gmail.com \
--cc=guile-user@gnu.org \
--cc=tmt_vdl@gmx.com \
/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).