-c gdbm.m.c -o gdbm.o In file included from /var/tmp/portage/dev-lisp/clisp-2.49-r100/work/clisp-2.49/modules/gdbm/gdbm.c:20:0: /var/tmp/portage/dev-lisp/clisp-2.49-r100/work/clisp-2.49/modules/gdbm/gdbm.c:782:5: error: ‘GDBM_ERR_UNKNOWN_ERROR’ undeclared here (not in a function) In file included from /var/tmp/portage/dev-lisp/clisp-2.49-r100/work/clisp-2.49/modules/gdbm/gdbm.c:9:0: /var/tmp/portage/dev-lisp/clisp-2.49-r100/work/clisp-2.49/modules/gdbm/gdbm.c: In function ‘open_gdbm’: /var/tmp/portage/dev-lisp/clisp-2.49-r100/work/clisp-2.49/modules/gdbm/gdbm.c:133:32: warning: passing argument 5 of ‘gdbm_open’ from incompatible pointer type [-Wincompatible-pointer-types] ----------------------------------------------------------------- This is an unstable amd64 chroot image (named desktop_20170305-211735) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.9 [icedtea-7] 2) IcedTea JDK 7.2.6.9 [icedtea-bin-7] *) IcedTea JDK 3.3.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-7 [2] icedtea-bin-7 [3] icedtea-bin-8 system-vm
Created attachment 466952 [details] emerge-info.txt
Created attachment 466954 [details] config.log.tbz2
Created attachment 466956 [details] dev-lisp:clisp-2.49-r100:20170313-153833.log
Created attachment 466958 [details] emerge-history.txt
Created attachment 466960 [details] environment
Created attachment 466962 [details] etc.portage.tbz2
This is actually a bug in gdbm. I've submitted a patch to the maintainers - though they seem to have no public bug tracking mailing list or the like that I could reference. I'll attach a patch to bump the ebuild and include the patch here as well, but I need someone to change the description and assignee to gdbm's maintainer.
Created attachment 467022 [details, diff] Include gdbm patch and revbump.
same here. I was able to emerge it by disabling gdbm use flags: # echo "=dev-lisp/clisp-2.49-r100 -gdbm" >> /etc/portage/package.use/package.use
(In reply to Mihai Moldovan from comment #8) > Created attachment 467022 [details, diff] [details, diff] > Include gdbm patch and revbump. TuX /mnt/portage/sys-libs/gdbm # patch gdbm-1.13.ebuild a.patch The next patch would create the file gdbm-1.13.ebuild, which already exists! Assume -R? [n] R Apply anyway? [n] y patching file gdbm-1.13.ebuild Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file gdbm-1.13.ebuild.rej patching file gdbm-1.13-r1.ebuild (renamed from gdbm-1.13.ebuild) Hunk #1 succeeded at 23 with fuzz 2 (offset -1 lines).
The fix by ionic@ionic.de works. Please apply and commit.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dafbc798a1d73b3f625a9119334f16774db1c601 commit dafbc798a1d73b3f625a9119334f16774db1c601 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2017-10-13 11:18:18 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2017-10-13 12:17:44 +0000 sys-libs/gdbm: Fix a typo in gdbm.h Closes: https://bugs.gentoo.org/612530 Package-Manager: Portage-2.3.10, Repoman-2.3.3 .../files/gdbm-1.13-fix-a-typo-in-gdbm.h.patch | 21 +++++++ sys-libs/gdbm/gdbm-1.13-r1.ebuild | 70 ++++++++++++++++++++++ 2 files changed, 91 insertions(+)
*** Bug 634606 has been marked as a duplicate of this bug. ***
With the use of the patch from Mihai Moldovan, the clisp assembly was successful
No need to apply any patches any longer - the patch has been applied to the portage tree. Just make sure to sync up.
