Arch Linux User Repository

Important note: Is recommended to receive the following key before to install:

$ gpg --recv-keys DE7A44FAC7FB382D

Also is possible skip the verification, adding the flag for (e.g makepkg, yay) --skippgpcheck, --nopgpfetch, respectively.

Thank you very much, @carlosal1015, @Asuranceturix, and @Xavier. I have built the package correctly after the new revision published by @carlosal1015.

@mluque: You don't have to keep trying anymore: the maintainer, @carlosal1015, has published a new revision of the package including the patch (thanks!), you should be able to build it now.

@Xavier: Of course it is up to the maintainers to make changes to the AUR-published packages. However, I am not aware of any rule that says that I cannot modify a published AUR package for my own use, or discuss such modifications with other fellow users, as long as we don't complain to the maintainer about possible problems stemming from our (unsanctioned) modifications. Sometimes, with less-responsive maintainers (which is absolutely not the case here), it is the only way to keep things going. :)

@mluque and @Asuranceturix It is up to the maintainers to patch the package so it compiles correctly with the Arch Linux library versions.

Thank you very much, @Asuranceturix. I have tried several times, but it always ends up giving me an error. Probably Arch is not for me.

@mluque: In this case it is very easy since the original PKGBUILD already includes a patch and you can use it as a model. Just download the patch referenced by @xukailiang into a file in the same directory as the PKGBUILD, name it "gcc15.patch", for example, and do as the original PKGBUILD does with the "qt6.patch": you need to reference the new patch from "sources", put its checksum in "sha512sums" and add a new line to apply the patch in the "prepare" function.

Thank you, @Asuranceturix. I have never patched a package; I would have to learn how to do it.

@mluque: The patch suggested by @xukailiang comes from the upstream repository, and it will surely be included in the next release. In the meantime, I think it would be much nicer to AUR users to just apply it onto the existing release than making them build GCC 14, which takes a very, very long time.

Thank you very much, @xukaliang. Wouldn't it be better if the PKGBUILD file contained information about the version of gcc that allows original LyX sources to be compiled without errors?

I'm getting build error after upgrading to GCC 15, which can be fixed by this patch. It compiles successfully for me after applying this patch.

I am having next error when trying to install LyX.

mathed/MathParser.cpp: In function ‘std::ostream& lyx::{anonymous}::operator<<(std::ostream&, const Token&)’:
mathed/MathParser.cpp:373:35: error: ‘uint32_t’ does not name a type
  373 |                 os << static_cast<uint32_t>(t.character());
      |                                   ^~~~~~~~
mathed/MathParser.cpp:80:1: note: ‘uint32_t’ is defined in header ‘<cstdint>’; this is probably fixable by adding ‘#include <cstdint>’
   79 | #include "support/docstream.h"
  +++ |+#include <cstdint>
   80 | 
mathed/MathParser.cpp:375:42: error: ‘uint32_t’ does not name a type
  375 |                 os << '[' << static_cast<uint32_t>(t.character()) << ',' << t.cat() << ']';
      |                                          ^~~~~~~~
mathed/MathParser.cpp:375:42: note: ‘uint32_t’ is defined in header ‘<cstdint>’; this is probably fixable by adding ‘#include <cstdint>’
make[4]: *** [Makefile:2424: mathed/MathParser.o] Error 1
make[4]: Leaving directory '/home/manolo/.cache/yay/lyx/src/lyx-2.4.3/src'
make[3]: *** [Makefile:2614: all-recursive] Error 1
make[3]: Leaving directory '/home/manolo/.cache/yay/lyx/src/lyx-2.4.3/src'
make[2]: *** [Makefile:1707: all] Error 2
make[2]: Leaving directory '/home/manolo/.cache/yay/lyx/src/lyx-2.4.3/src'
make[1]: *** [Makefile:586: all-recursive] Error 1
make[1]: Leaving directory '/home/manolo/.cache/yay/lyx/src/lyx-2.4.3'
make: *** [Makefile:481: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: lyx-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
lyx - exit status 4