GDB 7.12 seems to compile fine with just a version bump and new sha256sums. Would it be worth considering switching to python 3 instead of 2? That would bring it inline with the system gdb, and it would make it easier to share gdbinit configs between them (e.g. installing gef or voltron). Seems to work fine with just a change in the dependencies and pointing at python3 in the configure command.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
Guile was updated to version 2.2.x around march 2017. It seems to me that building gdb from source still requires guile 2.0.x (which is also done in the official package in extra/gdb). I could successfully build arm-linux-gnueabihf-gdb with the following changes in the PKGBUILD: 1. Change line 11 to: depends=(xz ncurses expat python2 guile2.0) 2. In the configure step in line 22, add: --with-guile=guile-2.0 \