unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Faenza, Michael E" <mfaenza@mitre.org>
To: "bug-guile@gnu.org" <bug-guile@gnu.org>
Subject: Guile 1.9.10 Build Questions
Date: Tue, 13 Jul 2010 09:54:17 -0400	[thread overview]
Message-ID: <0111C34BD897FD41841D60396F2AD3D304BD729632@IMCMBX2.MITRE.ORG> (raw)

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

Hello,



I've attempted to build Guile 1.9.10 on a 32-bit installation of Ubuntu 9.10.  I cannot seem to successfully build using a call to 'make'.  I've worked through what I believe to be my full set of configuration issues.



Two items still trouble me:



1)      Configuration of Guile checks how to link with Readline.  In my case, configuration correctly determines that libreadline is available.  This happens to be a Readline v.6.1 installation.  However, I get a configure warning stating that Readline is too old and that I need v.2.1 or better.  I wonder if the checks that Guile is performing are appropriate for determining the suitability of the installed Readline library.



2)      'make' fails due to what primarily seems to be many undefined references to GC_ functions.  ffi_ types aren't also coming up with undefined references.  I believe I've set up appropriate environment variables for libffi and libgc.



Has anyone experienced either of these behaviors recently?  I realize I'm not including any output for you to analyze; I didn't want you to have to pour through my scripts or output.  I'm just hoping someone sees this and realizes I've made a common mistake and can point that out to me.



Thank you,

Michael Faenza






[-- Attachment #2: Type: text/html, Size: 5719 bytes --]

             reply	other threads:[~2010-07-13 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 13:54 Faenza, Michael E [this message]
2010-07-13 18:56 ` Guile 1.9.10 Build Questions Andy Wingo

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=0111C34BD897FD41841D60396F2AD3D304BD729632@IMCMBX2.MITRE.ORG \
    --to=mfaenza@mitre.org \
    --cc=bug-guile@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).