unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: Linking statically with libguile on Debian
Date: Fri, 10 May 2002 14:32:53 -0700	[thread overview]
Message-ID: <E176I0T-0000BC-00@giblet> (raw)
In-Reply-To: <E175aqu-0008TP-00@nemesis> (message from David Allouche on Thu, 9 May 2002 01:28:08 +0200)

   From: David Allouche <me@davidallouche.net>
   Date: Thu, 9 May 2002 01:28:08 +0200

   I am a TeXmacs developper and I currently have problems with
   statically linking a binary against libguile 1.4 on Debian.

probably you mean the libguile that was shipped w/ guile-1.4 (which on
my system turns out to be libguile.so.9.0.0 -- can you confirm?).

   /usr/local/guile-1.4/lib/libguile.a(dynl.o): In function 
   `sysdep_dynl_link':
   /home/david/Desktop/guile-core-1.4/libguile/dynl.c:243: undefined 
   reference to `lt_dlopenext'

   That problem is fixed if I add -lltdl to the link command.

libguile depends on libltdl, so it seems to me "-lltdl" should be added
to the "guile-config link" output.  historically, libltdl was embedded
(no longer the case w/ guile-1.4.1, guile-1.5.x, and later), so this was
not necessary.

   I also tried to compile the upstream guile-1.4 package, but
   compilation failed.

yes, guile-1.4 is known to be slightly broken.  if you are adventurous,
i would recommend playing w/ guile-1.4.1 (in cvs -- see script below).
fwiw, my setup is reproducible via:

  checkout-hack -a
  cd hack/core-1-4
  sh -x autogen.sh
  mkdir ../core-1-4.b ; cd ../core-1-4.b           # b for "build"
  ../core-1-4/configure -C --enable-maintainer-mode --with-threads
  make
  make check

which all depends on automake-1.5, autoconf-2.53, libtool-1.4.2
(installed under /usr/local).  w/ this i am working (slowly but maybe
faster w/ some help) towards guile-1.4.1 release.

see hack/core-1-4/NEWS, also available online:

  http://www.glug.org/snap/guile-core-1.4/NEWS
  http://www.glug.org/snap/	(generally)

for more info.

thi


______________________________________
#! /bin/sh -x
# Usage: checkout-hack
#        checkout-hack -a       # "all" includes branches
#
# Env var: CVSROOT

CVSROOT=${CVSROOT-':pserver:anoncvs@subversions.gnu.org:/cvsroot/guile'}
export CVSROOT

branches="1-4 1-6"

cvs co hack

if [ x"$1" = x-a ] ; then
    cd hack
    for branch in $branches ; do
        cvs co -d core-$branch -r branch_release-$branch core
    done
fi

# checkout-hack ends here

_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


      reply	other threads:[~2002-05-10 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 23:28 Linking statically with libguile on Debian David Allouche
2002-05-10 21:32 ` Thien-Thi Nguyen [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=E176I0T-0000BC-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-user@gnu.org \
    --cc=ttn@glug.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).