Hi! The change broke compilation of www-servers/gatling (bug #672332) 0.31 # qlist dev-libs/libowfat | fgrep include | sort /usr/include/libowfat/array.h /usr/include/libowfat/buffer.h [..] /usr/include/libowfat/uint64.h /usr/include/libowfat/va_narg.h 0.32 # qlist dev-libs/libowfat | fgrep include | sort /usr/include/libowfat/libowfat/array.h /usr/include/libowfat/libowfat/buffer.h [..] /usr/include/libowfat/libowfat/uint64.h /usr/include/libowfat/libowfat/va_narg.h ^^^^^^^^^ Is the change in header location intended?
(In reply to Sebastian Pipping from comment #0) > Is the change in header location intended? Hard to tell. At least this is caused by the following upstream change: > move headers to <libowfat/> upon install But it is also possible that we only have to adjust > INCLUDEDIR="/usr/include/libowfat" in our ebuild. I'll look into it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8640288c58316fd8062caf4ce3ec546dc5da690 commit e8640288c58316fd8062caf4ce3ec546dc5da690 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-12-01 18:46:29 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-12-01 18:46:41 +0000 dev-libs/libowfat: fix header location ...and improve Gentoo prefix support. Closes: https://bugs.gentoo.org/672342 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> .../{libowfat-0.32.ebuild => libowfat-0.32-r1.ebuild} | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-)
Thanks for the quick fix!