bug-guile
[Top][All Lists]
Advanced

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

Re: Intel Mac-mini OSX 10.5.1 guile test results


From: Roger Mc Murtrie
Subject: Re: Intel Mac-mini OSX 10.5.1 guile test results
Date: Fri, 25 Jan 2008 12:31:10 +1100

I'm having trouble implementing the patches.
The problem seems to occur when autoconf runs.
It generates configure with a CR after the 3 in the guile version number:

#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.61 for guile-readline -n 1.8.3
.
#

From scratch, if I just do the configure.in patch, configure works OK
When I make a change to readline.c, then make distclean the following occurs:

make distclean
cd . && /bin/sh /Applications_Packages/guile-1.8.3/guile-readline/ missing --run aclocal-1.10 cd . && /bin/sh /Applications_Packages/guile-1.8.3/guile-readline/ missing --run automake-1.10 --foreign cd . && /bin/sh /Applications_Packages/guile-1.8.3/guile-readline/ missing --run autoconf
/bin/sh ./config.status --recheck
running CONFIG_SHELL=/bin/sh /bin/sh ./configure --no-create --no- recursion
./configure: line 4: .: filename argument required
.: usage: . filename [arguments]
make: *** [config.status] Error 2

If I manually correct this, I get failure when conftest tries to run as it generates confdefs with the same problem

I can't figure out where its doing this.
Can you suggest where the problem might be?

Thanks
Roger


On 25/01/2008, at 9:46 AM, Neil Jerram wrote:

Roger Mc Murtrie <address@hidden> writes:

Result of latest
make distclean
./configure
make

gcc -dynamiclib  -o .libs/libguilereadline-
v-17.17.0.2.dylib  ............

Undefined symbols:
 "_rl_get_keymap", referenced from:
     _scm_init_readline in readline.o
 "_rl_get_keymap_name", referenced from:
     _scm_init_readline in readline.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[4]: *** [libguilereadline-v-17.la] Error 1

Thanks.  I think the patch below should fix those.

Regards,
    Neil






reply via email to

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