Arch Linux User Repository

The patch I just added should ensure no dependency errors occur, and the documentation will not be built by this package, but is available with https://aur.archlinux.org/packages/vectorscan-docs

Well... that's one possible solution I could adopt for now, but I'd prefer to patch the makefile to remove those dependencies, which would build just vectorscan without the documentation, and I have provided a separate package vectorscan-docs for those.

I'll get onto writing that patch later today.

@marcool04 Yes, I was missing doxygen. Thank you ! Shouldn't that be a dependency ?

Well that is quite a different error isn't it, not "the error"...

What you are running into is the second point I raised under "Doxygen is handled similarly" in the issue I reported upstream, about doxygen.

Unless I'm mistaken, I would imagine that you do not have doxygen installed but do have python-sphinx and python-breathe installed. That is why this error is happening: because there is a logic error in the tests for which packages are installed in the makefile, upstream.

I'll think about how this can best be mitigated here while waiting for upstream to fix this.

In the mean time if you really must proceed, installing doxygen might fix this on your end @filiplaurentiu.

@marcool04

-- Configuring done (3.8s) -- Generating done (0.1s) -- Build files have been written to: /home/filip/.cache/paru/clone/vectorscan/src/build ninja: error: 'doc/dev-reference/dev-reference-doxygen', needed by 'doc/dev-reference/CMakeFiles/dev-reference-man', missing and no known rule to make it ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'vectorscan-5.4.13-3': error: packages failed to build: vectorscan-5.4.13-3 This is the error

@jnbrains what I mean by a "non-clean" system is that you are not building this package in a clean chroot; please see the Arch wiki for an explanation of this. When built in a clean chroot, this package does not give an error, because in a clean chroot you only install the requirements for making the package and its deps, and so you would have had no sphinx, and the docs would not have been built. See my issue on github upstream for an explanation of what is going on exactly that causes this behaviour.

@filiplaurentiu you have python-breathe installed and you see the same error? As in:

sphinx.errors.ExtensionError: Could not import extension breathe (exception: No module named 'breathe')

That would be strange...

I have python-breathe installed and I still get the error

Thanks for all the work.

Can you clarify for me the "non-clean system that must have python-sphinx installed but not python-breathe" conclusion? Yes, python-sphinx was installed already as a dependency for other packages. BUT python-breathe is not a dep for python-sphinx (9.1.0-1). So how can having the python-breathe package missing make it a not-clean system/special case?

p.s. I always liked the idea of docs in a separate package, like it was in the distros I used in the 'olden' days. Don't burden the tools with docs - whoever wants the docs should install them separately. A clean and elegant approach.

Ok, so I think what is happening is that you are building on a non-clean system which must have python-sphinx installed but not python-breathe. This means the configuration utility finds sphinx, and configures the build to generate the API reference documentation, but then fails, because to do that you would also need python-breathe.

So there are basically two different levels which need action here:

1) Upstream should be notified so the configuration step can do a better job of checking that everything which is needed to build the docs is present before going ahead and trying to make them.

=> I've gone ahead and created an issue upstream [1]

2) We should consider how to manage this in the PKGBUILD as far as Arch Linux goes.

=> I have taken a close look at the docs in question, and they are quite a bit more than a simple man page, since they include a full set of rich html docs for the entire API. My preference therefore is not to add the makedeps for the docs to this package, as these are not really needed, as demonstrated by the installation succeeding in a clean chroot. Rather, since it might indeed be useful to have the docs available, I think these should live in a separate package, so I have created vectorscan-docs for this [2].

Thanks again for finding this issue and reporting it.

Cheers,

Mark.

[1] https://github.com/VectorCamp/vectorscan/issues/411

[2] https://aur.archlinux.org/packages/vectorscan-docs

thanks for the quick reply.

here's the error/issue without having python-breathe package installed:

skip
[438/438] Building man page reference with Sphinx
FAILED: [code=2] doc/dev-reference/CMakeFiles/dev-reference-man SKIP/makepkg/vectorscan/src/build/doc/dev-reference/CMakeFiles/dev-reference-man
cd SKIP/makepkg/vectorscan/src/build/doc/dev-reference && /usr/bin/sphinx-build -b man -c SKIP/makepkg/vectorscan/src/build/doc/dev-reference -d SKIP/makepkg/vectorscan/src/build/doc/dev-reference/_doctrees SKIP/makepkg/vectorscan/src/vectorscan-vectorscan-5.4.13/doc/dev-reference SKIP/makepkg/vectorscan/src/build/doc/dev-reference/man
skip
sphinx.errors.ExtensionError: Could not import extension breathe (exception: No module named 'breathe')