guile-2.0.0 build error on OS X 10.6.6

guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

Hi, Trying to install guile-2.0.0 on OS X 10.6.6 but make dies with
the following error.

  CCLD   libguile-2.0.la
ld: pointer in read-only segment not allowed in slidable image, used
in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)
collect2: ld returned 1 exit status
make[3]: *** [libguile-2.0.la] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Any help appreciated.

Thanks,
Mike

Re: guile-2.0.0 build error on OS X 10.6.6

[Andy Wingo]

On Sun 20 Feb 2011 21:20, Michael Ellis <michael.f.ellis@gmail.com> writes:

> Hi, Trying to install guile-2.0.0 on OS X 10.6.6 but make dies with
> the following error.
>
>   CCLD   libguile-2.0.la
> ld: pointer in read-only segment not allowed in slidable image, used
> in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)
> collect2: ld returned 1 exit status
> make[3]: *** [libguile-2.0.la] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2

Wild, I haven't seen that one.  Can you send gcc --version, the
compilation line that failed (from make V=1), your CFLAGS/CPPFLAGS, and
the CFLAGS/CPPFLAGS/configure arguments you used to build gmp.

Thanks,

Andy
-- 
http://wingolog.org/

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Sun, Feb 20, 2011 at 4:37 PM, Andy Wingo <wingo@pobox.com> wrote:
> Wild, I haven't seen that one.  Can you send gcc --version, the
> compilation line that failed (from make V=1), your CFLAGS/CPPFLAGS, and
> the CFLAGS/CPPFLAGS/configure arguments you used to build gmp.

Hi Andy,

Thanks for the quick response!  I'm suspecting this has something to
do with MacPorts because I found some reports of the same error text
(in a different context) and some discussion to the effect that if
you're using MacPorts you shouldn't have anything in /usr/local/.   I
do have a number of MacPorts packages installed in /opt/local/.  OTOH,
I thought the whole point of MacPorts putting everything in a separate
directory was to avoid this sort of problem.  Anyway, here's the most
of the info you requested.  I don't have the config.log for gmp; it
was installed some time ago.  I'll re-install it and either send you
the flags or let you know in case that fixes the problem.

Thanks,
Mike

gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)

------------------------------------
Error line from make
------------------------------------
make V=1
libtool: link: gcc -std=gnu99 -dynamiclib  -o
.libs/libguile-2.0.22.dylib  .libs/libguile_2.0_la-alist.o
.libs/libguile_2.0_la-arbiters.o .libs/libguile_2.0_la-array-handle.o
.libs/libguile_2.0_la-array-map.o .libs/libguile_2.0_la-arrays.o
.libs/libguile_2.0_la-async.o .libs/libguile_2.0_la-backtrace.o
.libs/libguile_2.0_la-boolean.o .libs/libguile_2.0_la-bitvectors.o
.libs/libguile_2.0_la-bytevectors.o .libs/libguile_2.0_la-chars.o
.libs/libguile_2.0_la-control.o .libs/libguile_2.0_la-continuations.o
.libs/libguile_2.0_la-debug.o .libs/libguile_2.0_la-deprecated.o
.libs/libguile_2.0_la-deprecation.o .libs/libguile_2.0_la-dynwind.o
.libs/libguile_2.0_la-eq.o .libs/libguile_2.0_la-error.o
.libs/libguile_2.0_la-eval.o .libs/libguile_2.0_la-evalext.o
.libs/libguile_2.0_la-expand.o .libs/libguile_2.0_la-extensions.o
.libs/libguile_2.0_la-feature.o .libs/libguile_2.0_la-fluids.o
.libs/libguile_2.0_la-foreign.o .libs/libguile_2.0_la-fports.o
.libs/libguile_2.0_la-frames.o .libs/libguile_2.0_la-gc-malloc.o
.libs/libguile_2.0_la-gc.o .libs/libguile_2.0_la-gdbint.o
.libs/libguile_2.0_la-gettext.o
.libs/libguile_2.0_la-generalized-arrays.o
.libs/libguile_2.0_la-generalized-vectors.o
.libs/libguile_2.0_la-goops.o .libs/libguile_2.0_la-gsubr.o
.libs/libguile_2.0_la-guardians.o .libs/libguile_2.0_la-hash.o
.libs/libguile_2.0_la-hashtab.o .libs/libguile_2.0_la-hooks.o
.libs/libguile_2.0_la-i18n.o .libs/libguile_2.0_la-init.o
.libs/libguile_2.0_la-inline.o .libs/libguile_2.0_la-instructions.o
.libs/libguile_2.0_la-ioext.o .libs/libguile_2.0_la-keywords.o
.libs/libguile_2.0_la-list.o .libs/libguile_2.0_la-load.o
.libs/libguile_2.0_la-macros.o .libs/libguile_2.0_la-mallocs.o
.libs/libguile_2.0_la-memoize.o .libs/libguile_2.0_la-modules.o
.libs/libguile_2.0_la-null-threads.o .libs/libguile_2.0_la-numbers.o
.libs/libguile_2.0_la-objcodes.o .libs/libguile_2.0_la-objprop.o
.libs/libguile_2.0_la-options.o .libs/libguile_2.0_la-pairs.o
.libs/libguile_2.0_la-poll.o .libs/libguile_2.0_la-ports.o
.libs/libguile_2.0_la-print.o .libs/libguile_2.0_la-procprop.o
.libs/libguile_2.0_la-procs.o .libs/libguile_2.0_la-programs.o
.libs/libguile_2.0_la-promises.o .libs/libguile_2.0_la-r6rs-ports.o
.libs/libguile_2.0_la-random.o .libs/libguile_2.0_la-rdelim.o
.libs/libguile_2.0_la-read.o .libs/libguile_2.0_la-root.o
.libs/libguile_2.0_la-rw.o .libs/libguile_2.0_la-scmsigs.o
.libs/libguile_2.0_la-script.o .libs/libguile_2.0_la-simpos.o
.libs/libguile_2.0_la-smob.o .libs/libguile_2.0_la-sort.o
.libs/libguile_2.0_la-srcprop.o .libs/libguile_2.0_la-srfi-1.o
.libs/libguile_2.0_la-srfi-4.o .libs/libguile_2.0_la-srfi-13.o
.libs/libguile_2.0_la-srfi-14.o .libs/libguile_2.0_la-srfi-60.o
.libs/libguile_2.0_la-stackchk.o .libs/libguile_2.0_la-stacks.o
.libs/libguile_2.0_la-stime.o .libs/libguile_2.0_la-strings.o
.libs/libguile_2.0_la-strorder.o .libs/libguile_2.0_la-strports.o
.libs/libguile_2.0_la-struct.o .libs/libguile_2.0_la-symbols.o
.libs/libguile_2.0_la-threads.o .libs/libguile_2.0_la-throw.o
.libs/libguile_2.0_la-trees.o .libs/libguile_2.0_la-uniform.o
.libs/libguile_2.0_la-values.o .libs/libguile_2.0_la-variable.o
.libs/libguile_2.0_la-vectors.o .libs/libguile_2.0_la-version.o
.libs/libguile_2.0_la-vm.o .libs/libguile_2.0_la-vports.o
.libs/libguile_2.0_la-weaks.o .libs/dynl.o .libs/filesys.o
.libs/posix.o .libs/net_db.o .libs/socket.o .libs/regex-posix.o
-Wl,-force_load,../lib/.libs/libgnu.a  -L/usr/local/lib
/usr/local/lib/libgc.dylib -lpthread /usr/local/lib/libffi.dylib
/usr/local/lib/libunistring.dylib -liconv /usr/local/lib/libgmp.a
-lltdl -lm  -O2   -install_name  /usr/local/lib/libguile-2.0.22.dylib
-compatibility_version 23 -current_version 23.0 -Wl,-single_module
ld: pointer in read-only segment not allowed in slidable image, used
in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)
collect2: ld returned 1 exit status

---------------------------------------
FLAGS from guile-2.0.0 config.log
---------------------------------------

cat config.log | grep FLAGS
ac_cv_env_BDW_GC_CFLAGS_set=
ac_cv_env_BDW_GC_CFLAGS_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBFFI_CFLAGS_set=
ac_cv_env_LIBFFI_CFLAGS_value=
pkg_cv_BDW_GC_CFLAGS='-I/usr/local/include  '
pkg_cv_LIBFFI_CFLAGS='-I/usr/local/lib/libffi-3.0.9/include  '
BDW_GC_CFLAGS='-I/usr/local/include  '
CFLAGS='-I/usr/local/include   -g -O2'
CPPFLAGS='-I/usr/local/include'
GCC_CFLAGS=' -Wall -Wmissing-prototypes -Wdeclaration-after-statement
-Wundef -Wswitch-enum'
GNU_LD_FLAGS=''
GUILE_CFLAGS='-I/usr/local/include -D_THREAD_SAFE '
LDFLAGS=''
LIBFFI_CFLAGS='-I/usr/local/lib/libffi-3.0.9/include  '
PTHREAD_CFLAGS='-D_THREAD_SAFE '
WARN_CFLAGS=''

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Sun, Feb 20, 2011 at 5:17 PM, Michael Ellis
<michael.f.ellis@gmail.com> wrote:
>  I don't have the config.log for gmp; it
> was installed some time ago.  I'll re-install it and either send you
> the flags or let you know in case that fixes the problem.

Reinstalling gmp made things slightly worse.  Building guile now fails
while compiling libibguile_2.0_la-vm.lo

Here's make output  for guile followed by the FLAGS in config.log for gmp.

Thanks,
Mike

bash-3.2$ make V=1
...
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H
-DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib
-I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include
-I/usr/local/include -D_THREAD_SAFE -Wall -Wmissing-prototypes
-Wdeclaration-after-statement -Wundef -Wswitch-enum
-fvisibility=hidden -I/usr/local/include -g -O2 -MT
libguile_2.0_la-vm.lo -MD -MP -MF .deps/libguile_2.0_la-vm.Tpo -c vm.c
-o libguile_2.0_la-vm.o >/dev/null 2>&1
make[3]: *** [libguile_2.0_la-vm.lo] Error 1

----------------------
FLAGS IN gmp/config.log
----------------------
bash-3.2$ cat config.log | grep FLAGS
CFLAGS=(unset)
CPPFLAGS=(unset)
CFLAGS=-O2 -pedantic -m64 -mtune=core2 -march=core2
CPPFLAGS=
GMP_LDFLAGS=
CXXFLAGS=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_YFLAGS_set=
ac_cv_env_YFLAGS_value=
ASMFLAGS=''
CFLAGS='-O2 -pedantic -m64 -mtune=core2 -march=core2'
CPPFLAGS=''
CXXFLAGS='-g -O2'
FFLAGS='-g -O2'
GMP_LDFLAGS=''
LDFLAGS=''
LIBGMPXX_LDFLAGS=''
LIBGMP_LDFLAGS=''
YFLAGS=''

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

On 20 Feb 2011, at 23:17, Michael Ellis wrote:

> ... I'm suspecting this has something to
> do with MacPorts because I found some reports of the same error text
> (in a different context) and some discussion to the effect that if
> you're using MacPorts you shouldn't have anything in /usr/local/.

When using the MacPorts Mac installer, it adds its paths in front of PATH. I have /usr/local/ before. The full $PATH:
$HOME/bin:/usr/local/bin:/usr/local/X11R6/bin:/usr/local/git/bin:/usr/local/texlive/2010/bin/x86_64-darwin:/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

If you think there is a problem with MacPorts, change PATH, or move /opt temporarily to another name. I used gmp-5.0.1, and that worked fine.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

>
> If you think there is a problem with MacPorts, change PATH, or move /opt temporarily to another name. I used gmp-5.0.1, and that worked fine.
>

Thanks for the advice, Hans, it was worth trying but changing the PATH
seems to have no effect. I'm still getting the error building
ibguile_2.0_la-vm.o that appeared after I re-installed gmp 5.

libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H
-DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib
-I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include
-I/usr/local/include -D_THREAD_SAFE -Wall -Wmissing-prototypes
-Wdeclaration-after-statement -Wundef -Wswitch-enum
-fvisibility=hidden -I/usr/local/include -g -O2 -MT
libguile_2.0_la-vm.lo -MD -MP -MF .deps/libguile_2.0_la-vm.Tpo -c vm.c
-o libguile_2.0_la-vm.o >/dev/null 2>&1
make[3]: *** [libguile_2.0_la-vm.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

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/bug-guile@gnu.org/msg05621.html ), except
that I'm not seeing the seg fault message with "make V=1".

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.

Thanks,
Mike

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

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/bug-guile@gnu.org/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.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 11:47 AM, Hans Aberg <haberg-1@telia.com> 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/bug-guile@gnu.org/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

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

On 21 Feb 2011, at 18:03, Michael Ellis wrote:

>> 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.
...
> 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.
...
> 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?

I used readline-6.1, and I do not try to link against any MacPorts stuff.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 12:26 PM, Hans Aberg <haberg-1@telia.com> wrote:
>> 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?
>
> I used readline-6.1, and I do not try to link against any MacPorts stuff.

I installed readline 6.2 from tarball just now and the build
completed.  That's the good news.  The bad news is that guile is
segfaulting on bootup and it looks like readline is the culprit.

michael-elliss-macbook:guile-2.0.0 mellis$ gdb guile
---------- <snip> --------------
(gdb) run
Starting program: /usr/local/bin/guile
Reading symbols for shared libraries .++++++++...... done
Reading symbols for shared libraries ... done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000001a2ce98
0x00007fff819267f0 in strncmp ()
(gdb) bt
#0  0x00007fff819267f0 in strncmp ()
#1  0x00000001019fe684 in init_bouncing_parens [inlined] () at
/Users/mellis/Downloads/guile-2.0.0/guile-readline/readline.c:445
#2  0x00000001019fe684 in scm_init_readline () at readline.c:575
---------- <snip> --------------
#28 0x0000000100043df7 in scm_boot_guile (argc=<value temporarily
unavailable, due to optimizations>, argv=<value temporarily
unavailable, due to optimizations>, main_func=<value temporarily
unavailable, due to optimizations>, closure=<value temporarily
unavailable, due to optimizations>) at init.c:329
#29 0x0000000100000ed2 in main (argc=<value temporarily unavailable,
due to optimizations>, argv=<value temporarily unavailable, due to
optimizations>) at guile.c:70
(gdb)

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 12:34 PM, Michael Ellis
<michael.f.ellis@gmail.com> wrote:
> On Mon, Feb 21, 2011 at 12:26 PM, Hans Aberg <haberg-1@telia.com> wrote:
>>> 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?
>>
>> I used readline-6.1, and I do not try to link against any MacPorts stuff.
>
> I installed readline 6.2 from tarball just now and the build
> completed.  That's the good news.  The bad news is that guile is
> segfaulting on bootup and it looks like readline is the culprit.
>
> michael-elliss-macbook:guile-2.0.0 mellis$ gdb guile
> ---------- <snip> --------------
> (gdb) run
> Starting program: /usr/local/bin/guile
> Reading symbols for shared libraries .++++++++...... done
> Reading symbols for shared libraries ... done
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000001a2ce98
> 0x00007fff819267f0 in strncmp ()
> (gdb) bt
> #0  0x00007fff819267f0 in strncmp ()
> #1  0x00000001019fe684 in init_bouncing_parens [inlined] () at
> /Users/mellis/Downloads/guile-2.0.0/guile-readline/readline.c:445
> #2  0x00000001019fe684 in scm_init_readline () at readline.c:575
> ---------- <snip> --------------
> #28 0x0000000100043df7 in scm_boot_guile (argc=<value temporarily
> unavailable, due to optimizations>, argv=<value temporarily
> unavailable, due to optimizations>, main_func=<value temporarily
> unavailable, due to optimizations>, closure=<value temporarily
> unavailable, due to optimizations>) at init.c:329
> #29 0x0000000100000ed2 in main (argc=<value temporarily unavailable,
> due to optimizations>, argv=<value temporarily unavailable, due to
> optimizations>) at guile.c:70
> (gdb)
>
Commenting out readline in my .guile avoids the segfault.

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

On 21 Feb 2011, at 18:48, Michael Ellis wrote:
> Commenting out readline in my .guile avoids the segfault.

I do not have a ~/.guile file.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 1:12 PM, Hans Aberg <haberg-1@telia.com> wrote:
> On 21 Feb 2011, at 18:48, Michael Ellis wrote:
>> Commenting out readline in my .guile avoids the segfault.
>
> I do not have a ~/.guile file.

I'm assuming readline works for you in guile.  How do you activate it?
My .guile had these lines:

(use-modules (ice-9 readline))
(activate-readline)

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

On 21 Feb 2011, at 19:17, Michael Ellis wrote:

>>> Commenting out readline in my .guile avoids the segfault.
>> 
>> I do not have a ~/.guile file.
> 
> I'm assuming readline works for you in guile.  How do you activate it?

I just assumed it would be activated automatically. I am not using Guile interactively, so I have not thought about it much.

> My .guile had these lines:
> 
> (use-modules (ice-9 readline))
> (activate-readline)

This works just fine.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 1:38 PM, Hans Aberg <haberg-1@telia.com> wrote:
>> (use-modules (ice-9 readline))
>> (activate-readline)
>
> This works just fine.
>

Thanks, that helps narrow the search.  Sounds like it could be either
a 32 vs 64 problem or perhaps loading an old version of readline or
one of its dependencies.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

<michael.f.ellis@gmail.com> wrote:
> On Mon, Feb 21, 2011 at 1:38 PM, Hans Aberg <haberg-1@telia.com> wrote:
>>> (use-modules (ice-9 readline))
>>> (activate-readline)
>>
>> This works just fine.
>>
>
> Thanks, that helps narrow the search.  Sounds like it could be either
> a 32 vs 64 problem or perhaps loading an old version of readline or
> one of its dependencies.
>

I ran otool against libguile-2.0 and got the output below.  It looks
both modules are linked against compatible versions of dependent
libraries with only three of those libraries outside of
/usr/local/lib, namely, libSystem.B,  libiconv, and libltdl.  Those 3
are all in /usr/lib and I presume they are from Apple.  Do these
results look different from your installation?

michael-elliss-macbook:lib mellis$ otool -L libguile-2.0.dylib
libguile-2.0.dylib:
	/usr/local/lib/libguile-2.0.22.dylib (compatibility version 23.0.0,
current version 23.0.0)
	/usr/local/lib/libgc.1.dylib (compatibility version 2.0.0, current
version 2.3.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.1)
	/usr/local/lib/libffi.5.dylib (compatibility version 6.0.0, current
version 6.10.0)
	/usr/local/lib/libunistring.0.dylib (compatibility version 2.0.0,
current version 2.2.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/usr/local/lib/libgmp.10.dylib (compatibility version 11.0.0, current
version 11.1.0)
	/usr/lib/libltdl.7.dylib (compatibility version 9.0.0, current version 9.2.0)

michael-elliss-macbook:lib mellis$ otool -L libguilereadline-v-18.dylib
libguilereadline-v-18.dylib:
	/usr/local/lib/libguilereadline-v-18.18.dylib (compatibility version
19.0.0, current version 19.0.0)
	/usr/local/lib/libreadline.6.2.dylib (compatibility version 6.0.0,
current version 6.2.0)
	/usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current
version 5.4.0)
	/usr/local/lib/libguile-2.0.22.dylib (compatibility version 23.0.0,
current version 23.0.0)
	/usr/local/lib/libgc.1.dylib (compatibility version 2.0.0, current
version 2.3.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.1)
	/usr/local/lib/libffi.5.dylib (compatibility version 6.0.0, current
version 6.10.0)
	/usr/local/lib/libgmp.10.dylib (compatibility version 11.0.0, current
version 11.1.0)
	/usr/lib/libltdl.7.dylib (compatibility version 9.0.0, current version 9.2.0)
	/usr/local/lib/libunistring.0.dylib (compatibility version 2.0.0,
current version 2.2.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)

Re: guile-2.0.0 build error on OS X 10.6.6

[Hans Aberg]

On 21 Feb 2011, at 20:27, Michael Ellis wrote:

>>>> (use-modules (ice-9 readline))
>>>> (activate-readline)
>>> 
>>> This works just fine.
>> 
>> Thanks, that helps narrow the search.  Sounds like it could be either
>> a 32 vs 64 problem or perhaps loading an old version of readline or
>> one of its dependencies.
> 
> I ran otool against libguile-2.0 and got the output below.  It looks
> both modules are linked against compatible versions of dependent
> libraries with only three of those libraries outside of
> /usr/local/lib, namely, libSystem.B,  libiconv, and libltdl.  Those 3
> are all in /usr/lib and I presume they are from Apple.  Do these
> results look different from your installation?

Essentially, I alos have a libintl.8.dylib, and I used libreadline.6.1.

Also, when recompiling, I usually unpack again, because 'make clean' may be buggy.

Re: guile-2.0.0 build error on OS X 10.6.6

[Michael Ellis]

On Mon, Feb 21, 2011 at 3:10 PM, Hans Aberg <haberg-1@telia.com> wrote:
> On 21 Feb 2011, at 20:27, Michael Ellis wrote:
>
>>>>> (use-modules (ice-9 readline))
>>>>> (activate-readline)
>>>>
>>>> This works just fine.
>>>
>>> Thanks, that helps narrow the search.  Sounds like it could be either
>>> a 32 vs 64 problem or perhaps loading an old version of readline or
>>> one of its dependencies.
>>
>> I ran otool against libguile-2.0 and got the output below.  It looks
>> both modules are linked against compatible versions of dependent
>> libraries with only three of those libraries outside of
>> /usr/local/lib, namely, libSystem.B,  libiconv, and libltdl.  Those 3
>> are all in /usr/lib and I presume they are from Apple.  Do these
>> results look different from your installation?
>
> Essentially, I alos have a libintl.8.dylib, and I used libreadline.6.1.
>
> Also, when recompiling, I usually unpack again, because 'make clean' may be buggy.
>
>
Hmmm, I'm not making any progress on this so I'm going to defer it for
now.  Running guile-2.0 in emacs seems to work fine as far as editing
and interaction are concerned and I'd rather spend the time getting to
know the new features.  Thanks for helping me sort through the various
build issues!
Cheers,
Mike