From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: libltdl question
Date: Mon, 30 Sep 2002 11:11:53 -0500 [thread overview]
Message-ID: <87r8fbfody.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <1033334177.2089.19.camel@li.mine.nu> (Bo Forslund's message of "29 Sep 2002 23:16:17 +0200")
Bo Forslund <bo.forslund@abc.se> writes:
> I am trying to put together a guile 1.6.0 rpm package.So far
> everything is bundled in one big package just to have something to
> start with.
OK, though if you're interested in the long run, it'd be *really* nice
to have a proper rpm spec file in CVS, one that breaks out the
libraries into separate packages appopriately. Hopefully with a
ready-made spec file, we might get RH interested in switching
something more reasonable.
> I have a question about libltdl. Is it the same as the libltdl that
> comes with libtool? If libtool is installed should libltdl from
> guile replace the one from libtool?
Yes. No. Ideally guile should be built against your system's libltdl
and link against that. If your system has a libltdl-dev package, make
sure to install that before building guile -- with one caveat -- there
are some buggy versions of libltdl. We have a patch in our autogen.sh
file for one of the bugs...)
> Why is a libltdl made. Is it needed by guile? Can it be named
> guile-libltdl or something?
Guile depends on libltdl for loading shared libraries at runtime via
(dynamic-link "libfoo"). Ideally all apps on your system should use
the same libltdl shared library so they all have the same behaviors
(and can share lib and function ptrs internally without risk).
So the best arrangement would be for your system to have a good
version of libltdlX, and have your libguile12 rpm depend on that.
A "correct" packaging of guile 1.6.0 should probably look something
like this:
guile-1.6 (package with /usr/bin/guile -- depends on libguile12)
libguile12 (separate package for guile's main shared lib -- includes
includes share/guile/1.6.0/, etc.)
libguilesrfi-srfi-* (separate packages for each shared lib -- depend
on libguile12)
etc.
I'm gearing up to re-work debian's packages for 1.6.0, so I'll have a
really clear idea after that. debian's arrangement is mostly right
already, but there are some broken bits there too.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-30 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 21:16 libltdl question Bo Forslund
2002-09-30 16:11 ` Rob Browning [this message]
2002-09-30 21:55 ` Bo Forslund
2002-10-01 22:21 ` Marius Vollmer
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=87r8fbfody.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).