unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Peter Teeson <peter.teeson@me.com>
To: Peter Teeson <pteeson@me.com>
Cc: 13342@debbugs.gnu.org
Subject: bug#13342: Errors trying to build Guile 2.0.7
Date: Thu, 03 Jan 2013 21:18:47 -0500	[thread overview]
Message-ID: <B29FD5CD-E587-432E-8108-9959EDE3BCCB@me.com> (raw)
In-Reply-To: <BA2BEFFD-26D7-428B-A455-C7CDC2DB970C@me.com>

Hi Ludo':
Thanks for your reply and your explanation.

On 2013-01-03, at 10:22 AM, Ludovic Courtès wrote:
>> (A) I solved this one by installing GNU readline-6.2.
>> Prior to that it must have used Apple's deadline which didn't have the rl_get_keymap_name
>> function.
> 
> Yes, that’s because you were using the Readline “compatibility” layer of
> libeditline, which is shipped as part of MacOS.

>> You might wish to make a test for that function in configure and maybe make GNU readline a required lib?
> 
> There are tests checking for GNU Readline.  The problem is that
> libeditline attempts to replicate Readline’s API, but not quite, hence
> the problem.  That’s why ‘README’ insists on using GNU Readline.
Before I did/do anything I always read the README ;}
Somehow I missed the README insisting - I still don't see it there;}
There is a cryptic statement on page 1
"It will also use the libreadline library if it is available." 

and buried later on at line 413 (using BBEdit)
"guile-readline:
       The glue code for using GNU readline with Guile.  This
       will be build when configure can find a recent enough readline
       library on your system."

I agree there should be something mentioning the Mac situation and insisting on on GNU Readline. Where do you think it should be explicitly mentioned? In the Special Instructions For Some Systems section?

>> bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
>> FAIL: test-ffi
> 
> This is a known issue when building Guile with LLVM/Clang:
> 
> http://bugs.gnu.org/10015
> http://bugs.gnu.org/10681
> 
> It would be great if you could investigate.

I'd be glad to try and help but please give me pointers on how to approach this.
This will be a learning exercise for me as I am familiar with Xcode and it's debugger (GDB and LLDB) but have only used it developing Cocoa apps.

Care to suggest how I should approach things?

thanks and respect….

Peter






  parent reply	other threads:[~2013-01-04  2:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 20:39 bug#13342: Errors trying to build Guile 2.0.7 Peter Teeson
2013-01-03 15:22 ` Ludovic Courtès
     [not found]   ` <BA2BEFFD-26D7-428B-A455-C7CDC2DB970C@me.com>
2013-01-04  2:18     ` Peter Teeson [this message]
2013-01-04  2:21       ` Peter Teeson
2013-01-04 17:23         ` Ludovic Courtès
     [not found]           ` <895C23AD-DD0D-40FC-AD5F-6CEF52365444@me.com>
2013-01-08 16:08             ` bug#13386: Fwd: " Peter Teeson
2013-01-30 22:13               ` bug#13386: bug#13342: closed (Re: bug#13342: Errors trying to build Guile 2.0.7) , bug#13386: closed (Re: bug#13342: Errors trying to build Guile 2.0.7) Peter Teeson
2013-01-31 20:20                 ` Mark H Weaver
2013-02-01  2:05                   ` bug#13386: " Peter Teeson
2013-02-02 13:11                     ` Mark H Weaver
2013-02-03  0:05                       ` Peter Teeson
2013-02-03  3:22                         ` bug#13386: " Mark H Weaver
2013-01-08 16:08             ` bug#13342: [PARTIALLY SOLVED] bug#13342: Errors trying to build Guile 2.0.7 Peter Teeson
2013-01-27 14:11               ` Ludovic Courtès
2013-01-27 21:35                 ` Peter Teeson
2013-01-28  1:46                 ` Mark H Weaver
2013-01-28  2:40                   ` Peter Teeson
2013-01-28 12:56                   ` Ludovic Courtès
2013-01-28 16:39                     ` Peter Teeson
2013-01-28 16:55                       ` Ludovic Courtès
2013-01-08 16:30 ` bug#13342: Errors trying to build Guile 2.0.7 [PARTIALLY SOLVED] Peter Teeson
2013-01-30  8:34 ` bug#13342: Errors trying to build Guile 2.0.7 Mark H Weaver
2013-01-30 21:37   ` Ludovic Courtès

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=B29FD5CD-E587-432E-8108-9959EDE3BCCB@me.com \
    --to=peter.teeson@me.com \
    --cc=13342@debbugs.gnu.org \
    --cc=pteeson@me.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).