bug#19237: Guile-2.0.11 OS X 10.10.1 build error

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Hans Aberg]

I get a build error [1] with guile-2.0.11 on OS X 10.10.1. It looks like an illegal int to pointer conversion cause a name to not be defined, and then the linking fails.


1. make
...
Making all in guile-readline
  SNARF  readline.x
/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-am
  CC       readline.lo
../../guile-2.0.11/guile-readline/readline.c:433:16: warning: implicit declaration of function 'rl_get_keymap_name' is invalid in C99
      [-Wimplicit-function-declaration]
  if (strncmp (rl_get_keymap_name (rl_get_keymap ()), "vi", 2))
               ^
../../guile-2.0.11/guile-readline/readline.c:433:16: warning: incompatible integer to pointer conversion passing 'int' to parameter of type 'const char *'
      [-Wint-conversion]
  if (strncmp (rl_get_keymap_name (rl_get_keymap ()), "vi", 2))
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/string.h:84:26: note: passing argument to parameter here
int      strncmp(const char *, const char *, size_t);
                             ^
2 warnings generated.
  CCLD     libguilereadline-v-18.la
Undefined symbols for architecture x86_64:
  "_rl_get_keymap_name", referenced from:
      _scm_init_readline in readline.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [libguilereadline-v-18.la] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Ludovic Courtès]

Could it be because Guile is being compiled against libeditline instead
of GNU Readline?

Readline support in Guile requires GNU Readline.

Thanks,
Ludo’.

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Hans Aberg]

> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> Could it be because Guile is being compiled against libeditline instead
> of GNU Readline?
> 
> Readline support in Guile requires GNU Readline.

It looked as though that the readline in the Guile distribution is too old - no other readline installed on the system. I just installed the latest GNU readline into /usr/local/, and then Guile compiled.

Another dependency not mentioned in the INSTALL is that texi2pdf must be a recent version, otherwise conversion to PDF does not work - older version do not admit multiple files as argument or something.

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Ludovic Courtès]

Hans Aberg <haberg-1@telia.com> skribis:

>> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
>> 
>> Could it be because Guile is being compiled against libeditline instead
>> of GNU Readline?
>> 
>> Readline support in Guile requires GNU Readline.
>
> It looked as though that the readline in the Guile distribution is too
> old - no other readline installed on the system.

Actually there’s no Readline in Guile itself, just the guile-readline
bindings.

> I just installed the latest GNU readline into /usr/local/, and then
> Guile compiled.

OK, so I guess it was really libeditline’s Readline semi-compatibility
shim that was being used.

Closing this bug now.

Thanks,
Ludo’.

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Hans Aberg]

> On 4 Dec 2014, at 18:23, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> Hans Aberg <haberg-1@telia.com> skribis:
> 
>>> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
>>> 
>>> Could it be because Guile is being compiled against libeditline instead
>>> of GNU Readline?
>>> 
>>> Readline support in Guile requires GNU Readline.
>> 
>> It looked as though that the readline in the Guile distribution is too
>> old - no other readline installed on the system.
> 
> Actually there’s no Readline in Guile itself, just the guile-readline
> bindings.

I think the binding problem was that what Guile expected to be in one file, readline now has in several.

>> I just installed the latest GNU readline into /usr/local/, and then
>> Guile compiled.
> 
> OK, so I guess it was really libeditline’s Readline semi-compatibility
> shim that was being used.

Yes, there was some compatibility file, with the problem as above.

> Closing this bug now.

OK.

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Mark H Weaver]

Hans Aberg <haberg-1@telia.com> writes:

>> On 4 Dec 2014, at 18:23, Ludovic Courtès <ludo@gnu.org> wrote:
>> 
>> Hans Aberg <haberg-1@telia.com> skribis:
>> 
>>>> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
>>>> 
>>>> Could it be because Guile is being compiled against libeditline instead
>>>> of GNU Readline?
>>>> 
>>>> Readline support in Guile requires GNU Readline.
>>> 
>>> It looked as though that the readline in the Guile distribution is too
>>> old - no other readline installed on the system.
>> 
>> Actually there’s no Readline in Guile itself, just the guile-readline
>> bindings.
>
> I think the binding problem was that what Guile expected to be in one
> file, readline now has in several.

Can you explain this more clearly?  What do you think Guile expects to
be in one file that "readline now has in several"?  Also, how did you
reach this conclusion, given that GNU Readline apparently wasn't
installed when the build failed?

FWIW, we regularly build the latest Guile with the latest Readline in
GNU Guix, and haven't run into this problem.

     Regards,
       Mark

bug#19237: Guile-2.0.11 OS X 10.10.1 build error

[Hans Aberg]

> On 5 Dec 2014, at 00:47, Mark H Weaver <mhw@netris.org> wrote:
> 
> Hans Aberg <haberg-1@telia.com> writes:
> 
>>> On 4 Dec 2014, at 18:23, Ludovic Courtès <ludo@gnu.org> wrote:
>>> 
>>> Hans Aberg <haberg-1@telia.com> skribis:
>>> 
>>>>> On 3 Dec 2014, at 23:21, Ludovic Courtès <ludo@gnu.org> wrote:
>>>>> 
>>>>> Could it be because Guile is being compiled against libeditline instead
>>>>> of GNU Readline?
>>>>> 
>>>>> Readline support in Guile requires GNU Readline.
>>>> 
>>>> It looked as though that the readline in the Guile distribution is too
>>>> old - no other readline installed on the system.
>>> 
>>> Actually there’s no Readline in Guile itself, just the guile-readline
>>> bindings.
>> 
>> I think the binding problem was that what Guile expected to be in one
>> file, readline now has in several.
> 
> Can you explain this more clearly?  What do you think Guile expects to
> be in one file that "readline now has in several"?  Also, how did you
> reach this conclusion, given that GNU Readline apparently wasn't
> installed when the build failed?

My impression was that Guile had some compatibility header in case readline isn’t installed. The missing names referred to several files, whereas in Guile, there was only one.

> FWIW, we regularly build the latest Guile with the latest Readline in
> GNU Guix, and haven't run into this problem.

On OS X, readline isn’t installed by default, which probably was the reason. The same with pkg-config:

I have one in /opt/ from MacPorts, but packages in /usr/local/ may not read it. It may be that case with GC. So one has to install pkg-config in /usr/local/. Then another problem is that the MacPorts installer patches ~/.profile, add /opt first in the searchpath. So one has to remember setting that correct, too.

The Guile INSTALL mentions pkg-config, but only after GC, though it must be installed before it, and does not say where to get it. It is a recursive package, so one has to get around that.