In file included from cmdline.h:35, from lomoco.c:25: lomoco.h:32:10: fatal error: stropts.h: No such file or directory 32 | #include <stropts.h> | ^~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-libressl-20190806-091828 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-1.36.0 * emerge -qpvO sys-apps/lomoco [ebuild N ] sys-apps/lomoco-1.0-r9
Created attachment 586326 [details] emerge-info.txt
Created attachment 586328 [details] emerge-history.txt
Created attachment 586330 [details] environment
Created attachment 586332 [details] etc.portage.tbz2
Created attachment 586334 [details] logs.tbz2
Created attachment 586336 [details] sys-apps:lomoco-1.0-r9:20190809-111211.log
Created attachment 586338 [details] temp.tbz2
Guys, the upstream is dead. Please remove lomoco from the tree. Thank you.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=92e3cb4eac88ff97268290ddcf9a764189dd8b8f commit 92e3cb4eac88ff97268290ddcf9a764189dd8b8f Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-08-14 20:22:40 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-08-14 20:22:40 +0000 package.mask: Last rite sys-apps/lomoco Bug: https://bugs.gentoo.org/691840 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 6 ++++++ 1 file changed, 6 insertions(+)
This package builds just fine after removing the offending #include line. (No definitions found in that header file are actually used in the LoMoCo source.) Just add this line in src_prepare(): sed -e '/^#include <stropts\.h>$/d' -i src/lomoco.h || die I'm still using LoMoCo to disable "SmartScroll" on my Logitech MX1000 Laser Mouse. I will move the ebuild to my local repository if it's removed from the Gentoo repo, but there's really no reason to remove it yet.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1448ec22a2c73f9975ba5255986ea34b90f2cc7b commit 1448ec22a2c73f9975ba5255986ea34b90f2cc7b Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-09-14 15:47:07 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-09-14 15:47:07 +0000 sys-apps/lomoco: Remove last-rited pkg Closes: https://bugs.gentoo.org/691840 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 6 - sys-apps/lomoco/Manifest | 1 - .../files/lomoco-1.0-gentoo-hardware-support.patch | 287 --------------------- .../lomoco/files/lomoco-1.0-updated-udev.patch | 95 ------- sys-apps/lomoco/files/lomoco-pm-utils-r1 | 7 - sys-apps/lomoco/files/lomoco.conf | 9 - sys-apps/lomoco/lomoco-1.0-r9.ebuild | 52 ---- sys-apps/lomoco/metadata.xml | 12 - 8 files changed, 469 deletions(-)
Okay. Thanks for totally ignoring my fix, which completely solves the only issue with this package. Into my local repo this goes. :/
Created attachment 699717 [details] lomoco-1.1.ebuild.tar.gz The old sys-apps/lomoco-1.0-r9 was using EAPI=4, which is no longer supported by autotools.eclass. Attached is a tarball containing a new sys-apps/lomoco-1.1.ebuild and associated files, for anyone still using this package.