unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: can't configure --with-libgmp-prefix; header search order
Date: Thu, 6 Aug 2009 02:45:41 -0400	[thread overview]
Message-ID: <875E2245-1A19-47E0-980C-02E4D8CF459D@raeburn.org> (raw)
In-Reply-To: <m3my6fbd8r.fsf@pobox.com>

On Aug 4, 2009, at 15:17, Andy Wingo wrote:
>> In config.log I see that it's not using the -L option when testing  
>> for
>> __gmpz_init:
>
> I think I've fixed this. Can you pull from git and give it another go?

Starting with the current git code, and fixing an autogen problem (on  
Mac OS X we want to run "glibtool" because "libtool" is some other  
program), configure with --with-libgmp-prefix seems to work fine.

Compilation fails, first for unrelated reasons:

cc1: warnings being treated as errors
../../libguile/srfi-13.c: In function ‘string_titlecase_x’:
../../libguile/srfi-13.c:2517: warning: comparison is always false due  
to limited range of data type
../../libguile/srfi-13.c:2517: warning: comparison is always false due  
to limited range of data type

If I disable -Werror with "make GCC_CFLAGS=", it gets a bit further,  
and then:

Making all in guile-readline
../libguile/guile-snarf -o readline.x ../../guile-readline/readline.c - 
DHAVE_CONFIG_H  -I. -I.. -I../../guile-readline/.. -I../../guile- 
readline/lib -I./lib  -g -O2
In file included from ../../guile-readline/readline.c:29:
../../guile-readline/../libguile.h:25:17: error: gmp.h: No such file  
or directory





      reply	other threads:[~2009-08-06  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04  9:26 can't configure --with-libgmp-prefix; header search order Ken Raeburn
2009-08-04 19:17 ` Andy Wingo
2009-08-06  6:45   ` Ken Raeburn [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=875E2245-1A19-47E0-980C-02E4D8CF459D@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=bug-guile@gnu.org \
    --cc=wingo@pobox.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).