Hello,

On Tue, 20 Sep 2016, Lars Wendler wrote:
>This is a call for testers. If you feel brave enough, please give
>bash-4.4 a shot and report all problems you might have with it.
>
>Add the following to you package.unmask file/directory:
>
>  =app-shells/bash-4.4*
>  =sys-libs/readline-7.0*

with basically no testing so far: builds ok.

>in order to get all readline reverse deps being built against new
>readline. Reporting those packages in our bug tracker [1] would be
>helpful.

Creating a new bug or what? [2] seems inappropriate.

>[2] https://bugs.gentoo.org/594496

I've found this that I guess has to do with the new readline:

>From the build.log of
    emerge -1 dev-lisp/clisp

====
[..]
 * Package:    dev-lisp/clisp-2.49-r8
 * Repository: gentoo
 * Maintainer: common-l...@gentoo.org
 * USE:        X abi_x86_64 amd64 berkdb elibc_glibc gdbm gtk
   kernel_linux pcre postgres readline threads unicode userland_GNU
   zlib
 * FEATURES:   ccache compressdebug nostrip preserve-libs sandbox
   splitdebug userpriv usersandbox
[..]
;; Loading file 
/var/tmp/portage/dev-lisp/clisp-2.49-r8/work/clisp-2.49/builddir/readline/readline.fas
 ...
*** - FFI::FIND-FOREIGN-VARIABLE: foreign variable #<FOREIGN-VARIABLE 
"rl_readline_state" #x000000000088B460> does not have the
      required size or alignment

./clisp-link: failed in 
/var/tmp/portage/dev-lisp/clisp-2.49-r8/work/clisp-2.49/builddir
Makefile:2621: recipe for target 'base' failed
make: *** [base] Error 1
[..]
====

# equery uses -i =dev-lisp/clisp-2.49-r8 | xargs echo
+X +berkdb -dbus -fastcgi +gdbm +gtk -hyperspec -pari +pcre +postgres
+readline +threads +unicode +zlib

So, something with 'rl_readline_state' and how clisp uses that has
changed that I won't dig into right now. Clisp maintainers?

That seems to be the only problem with readline-7.0/bash-4.4 on this
install (so far).

-dnh

-- 
  The use of COBOL cripples the mind; its teaching should,
  therefore, be regarded as a criminal offence.
                                         -- Edsger Wybe Dijkstra

Reply via email to