Arch Linux User Repository

This PKGBUILD can be installed as binary packages from [pro-audio-legacy].

@jhogan: The PKGBUILD is now also fixed and celt is added to the custom repo as well.

I commented out the line: git config submodule.jack.url "${srcdir}/headers"

and then it built

You are building with the wrong/ no headers then. I strongly advice against that.

Meanwhile I'd recommend just using the package as mentioned in https://aur.archlinux.org/pkgbase/jack#comment-860367

Build failures with latest git:

==> Starting prepare()... Submodule 'jack' (https://github.com/jackaudio/headers) registered for path 'jack' Cloning into '/home/james/.cache/yay/jack/src/jack/jack'... fatal: transport 'file' not allowed fatal: clone of '/home/james/.cache/yay/jack/src/headers' into submodule path '/home/james/.cache/yay/jack/src/jack/jack' failed Failed to clone 'jack'. Retry scheduled Cloning into '/home/james/.cache/yay/jack/src/jack/jack'... fatal: transport 'file' not allowed fatal: clone of '/home/james/.cache/yay/jack/src/headers' into submodule path '/home/james/.cache/yay/jack/src/jack/jack' failed Failed to clone 'jack' a second time, aborting ==> ERROR: A failure occurred in prepare(). Aborting...

presumably due to this: https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

I commented out the line: git config submodule.jack.url "${srcdir}/headers"

and then it built

@starfry: LOL, I realized I had changed this already for the unofficial binary repository, but forgot to commit/push the changes here... :S

This PKGBUILD can be installed as binary packages from [pro-audio-legacy].

@starfry: Yeah, that should be changed. It is a bit confusing as this package itself provides jack by being called jack, while pipewire-jack and jack2 both just "virtually" provide jack.

The "provides" definition for jack says it provides jack2. Doesn't that mean that a dependency on jack2 can be satisified by this package. If that's correct then it doesn't make sense... If I install "jack2-dbus" its dependency on 'jack2' can be satisfied by this package which is wrong and does not work.

I ended up with a system that had "jack2-dbus" and "jack" but not "jack2". I've been puzzling over why my system had jack on it after being rebuilt from scratch with jack2-dbus and I can only think this is the reason (I have a local repo of some packages which could have provided "jack" it without it needed to be built).

@HMlendea: No (see https://wiki.archlinux.org/title/Arch_User_Repository#Prerequisites). :)

I get this error: line 39: autoreconf: command not found

autoconf should be added as a build dependency. After installing that package, this builds successfully.

@WonderWoofy: No. jack has been dropped from [extra] and has been replaced with jack2. The tooling is just a little slow to catch up.