Arch Linux User Repository

PKGBUILD patch to 1.10.6: https://paste.debian.net/1289953/

pkg-config is contained in pkgconf which is expected to be installed on every system building packages since it is part of the base-devel group.

Hi, I think the package lacks a dependency: running makepkg -s didn't ask for pkg-config, but then the configuration phase of the building seems to require it

@mroethke thank you very much. We will see ;-)

@ra1nb0w I have disabled guile for now, but might reenable it if enough people complain.

From version 1.8 the current guile support has been deprecated. Therefore, I suggest to remove that cumbersome dependency or made a new mu-guile aur since from what I read in mu ml/issues it has very little usage. What do you think?

source: https://github.com/djcb/mu/blob/master/NEWS.org

@milouse Thanks for reminding me that arch-meson exists!

@prosoitos Unfortunately I cannot answer that question. I know next to nothing about emacs. But I do know that I do not do anything special in this package. If I had to guess I would say that meson does something different from autotools or something changed in 1.8. Since those problems seem to be new. I will do some digging tomorrow.

Hi,

2 errors mentioned in this issue in the mu repo might stem from the packaging here maybe?

Thank you!

Hi,

Is there a specific reason you don’t want to use the arch-meson wrapper in the prepare step? i.e. instead of the current prepare function, use something like:

prepare() {
    arch-meson -Dguile=enabled -Dreadline=enabled "$pkgname-$pkgver" build
}

@xeruf That file is (re)generated by a pacman hook on install. So it makes sense that it does not belong to any package. However, even when not building in a clean chroot I can not reproduce your issue. And I have no idea how or why that file could end up in the package.

@xavierbaez It looks like your gcc-libs package is to old. Please do a full upgrade and try again or ideally build in a clean chroot.