bug-guile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile-2.0.0 build error on OS X 10.6.6


From: Michael Ellis
Subject: Re: guile-2.0.0 build error on OS X 10.6.6
Date: Mon, 21 Feb 2011 12:03:43 -0500

On Mon, Feb 21, 2011 at 11:47 AM, Hans Aberg <address@hidden> wrote:
> On 21 Feb 2011, at 15:21, Michael Ellis wrote:
>
>> There's no other error message but I notice it looks very much like
>> the problem you reported in the recent "Compiling from GIT"  thread (
>> http://www.mail-archive.com/address@hidden/msg05621.html ), except
>> that I'm not seeing the seg fault message with "make V=1".
>
> This was only a problem with guile-1.9.15 and the GIT version from about this 
> time.
>
>> Were you able to resolve the problem on your system?  I'm going to try
>> updating my XCode installation from 3.2.4 to 3.2.5 in the hope that a
>> new version of GCC will fix the problem, but it seems like a long
>> shot.
>
> I am using Xcode 3.2.5,
>  gcc --version
>  i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)
> And there was no problem compiling guile-2.0.0.
>
> As for the problem above, it reported internal compiler segmentation fault.
>
>

Updating to XCode 3.2.5 and starting over by re-extracting guile-2.0.0
went much further toward success.   The vm compiled as well as the
majority of guile modules.   Currently dying while building
guile-readline.

Making all in guile-readline
  SNARF  readline.x
make  all-am
  CC     readline.lo
readline.c: In function 'init_bouncing_parens':
readline.c:445: warning: implicit declaration of function 'rl_get_keymap_name'
readline.c:445: warning: passing argument 1 of 'strncmp' makes pointer
from integer without a cast
  CCLD   libguilereadline-v-18.la
Undefined symbols:
  "_rl_get_keymap_name", referenced from:
      _scm_init_readline in readline.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[3]: *** [libguilereadline-v-18.la] Error 1

FWIW I had some previous troubles with guile 1.8 and readline that
turned out to be a 64 vs 32 bit issue.   As I recall, re-installing
readline from a tarball instead of from MacPorts cured that.  Any
thoughts as to whether this might be related?

Thanks again,
Mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]