From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-client/netsurf/
Date: Tue, 30 Jun 2020 13:10:07 +0000 (UTC) [thread overview]
Message-ID: <1593522476.77e589717e3fe5788ef0030d5cc4a2517670cc9a.mjo@gentoo> (raw)
commit: 77e589717e3fe5788ef0030d5cc4a2517670cc9a
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 30 13:07:37 2020 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Tue Jun 30 13:07:56 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77e58971
www-client/netsurf: fix build with USE="fbcon svg -svgtiny".
The build system for netsurf only does the pkg-config magic needed to
find librsvg's headers when it's building the GTK targets (and not
when it's building the framebuffer target). As a result, building the
framebuffer target can fail if you have USE="svg -svgtiny" set. This
commit disables librsvg while building and installing the framebuffer
target. Thanks are due to ernsteiswuerfel for the extensive testing
on bug 728994.
Bug: https://bugs.gentoo.org/728994
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
www-client/netsurf/netsurf-3.10-r1.ebuild | 28 +++++++++++++++++++++++-----
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git a/www-client/netsurf/netsurf-3.10-r1.ebuild b/www-client/netsurf/netsurf-3.10-r1.ebuild
index 1ac3219ccb8..62dea848e93 100644
--- a/www-client/netsurf/netsurf-3.10-r1.ebuild
+++ b/www-client/netsurf/netsurf-3.10-r1.ebuild
@@ -97,7 +97,15 @@ _emake() {
}
src_compile() {
- use fbcon && _emake TARGET=framebuffer
+ # The build system only runs pkg-config to find librsvg's include
+ # dir for the gtk targets. So if you try to build the framebuffer
+ # target with NETSURF_USE_RSVG=YES, the build crashes on failing to
+ # find rsvg.h. To work around that, we set NETSURF_USE_RSVG=NO. It
+ # might be possible to fall back to svgtiny with USE="svg -svgtiny"
+ # if svgtiny works in a framebuffer, but then our (R)DEPEND would
+ # need some mangling to ensure that svgtiny is installed.
+ use fbcon && _emake NETSURF_USE_RSVG=NO TARGET=framebuffer
+
use gtk2 && _emake TARGET=gtk2
use gtk && _emake TARGET=gtk3
}
@@ -111,19 +119,29 @@ src_install() {
-i "${WORKDIR}"/*/utils/git-testament.pl || die
if use fbcon ; then
- _emake TARGET=framebuffer DESTDIR="${D}" install
+ # See earlier comments about rsvg.h.
+ _emake NETSURF_USE_RSVG=NO TARGET=framebuffer DESTDIR="${D}" install
elog "framebuffer binary has been installed as netsurf-fb"
- make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-fb NetSurf-framebuffer netsurf "Network;WebBrowser"
+ make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-fb \
+ NetSurf-framebuffer \
+ netsurf \
+ "Network;WebBrowser"
fi
if use gtk2 ; then
_emake TARGET=gtk2 DESTDIR="${D}" install
elog "netsurf gtk2 version has been installed as netsurf-gtk2"
- make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-gtk2 NetSurf-gtk2 netsurf "Network;WebBrowser"
+ make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-gtk2 \
+ NetSurf-gtk2 \
+ netsurf \
+ "Network;WebBrowser"
fi
if use gtk ; then
_emake TARGET=gtk3 DESTDIR="${D}" install
elog "netsurf gtk3 version has been installed as netsurf-gtk3"
- make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-gtk3 NetSurf-gtk3 netsurf "Network;WebBrowser"
+ make_desktop_entry "${EPREFIX}"/usr/bin/netsurf-gtk3 \
+ NetSurf-gtk3 \
+ netsurf \
+ "Network;WebBrowser"
fi
insinto /usr/share/pixmaps
next reply other threads:[~2020-06-30 13:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:10 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 19:11 [gentoo-commits] repo/gentoo:master commit in: www-client/netsurf/ Jakov Smolić
2024-02-09 12:24 Michael Orlitzky
2024-01-19 9:31 Michael Orlitzky
2024-01-19 9:31 Michael Orlitzky
2023-08-15 0:26 Michael Orlitzky
2023-08-15 0:26 Michael Orlitzky
2023-08-14 21:15 Michael Orlitzky
2023-07-05 20:43 Michael Orlitzky
2023-07-05 20:43 Michael Orlitzky
2023-05-27 22:02 Michael Orlitzky
2022-08-26 10:46 Sam James
2022-03-22 18:43 Jakov Smolić
2022-03-16 23:46 Sam James
2022-03-16 23:45 Sam James
2022-03-16 2:39 Sam James
2022-03-16 2:23 Sam James
2022-03-16 1:03 Sam James
2022-03-16 1:01 Sam James
2022-03-16 1:01 Sam James
2021-11-20 15:34 Arthur Zamarin
2021-11-10 17:56 Jakov Smolić
2021-03-30 17:38 Sam James
2020-11-13 16:57 Sam James
2020-10-17 11:29 Joonas Niilola
2020-09-29 22:48 Sam James
2020-08-15 12:03 Michael Orlitzky
2020-07-19 10:43 Joonas Niilola
2020-07-15 14:01 Michael Orlitzky
2020-07-05 8:40 Sergei Trofimovich
2020-06-29 17:08 Michael Orlitzky
2020-06-29 1:26 Michael Orlitzky
2020-06-29 1:26 Michael Orlitzky
2019-12-10 8:06 Joonas Niilola
2019-12-10 6:35 Joonas Niilola
2019-12-05 8:03 Joonas Niilola
2019-12-04 14:49 Joonas Niilola
2019-09-23 8:07 Michał Górny
2019-07-05 19:05 Virgil Dupras
2019-02-17 17:46 Sergei Trofimovich
2019-02-07 13:08 Virgil Dupras
2018-11-13 18:13 Virgil Dupras
2018-11-07 19:48 Virgil Dupras
2018-10-21 20:54 Virgil Dupras
2018-10-19 8:51 Michał Górny
2017-01-26 7:35 Michael Weber
2016-07-25 17:45 Chí-Thanh Christopher Nguyễn
2016-05-07 21:44 Michael Weber
2016-03-03 1:03 Michael Weber
2016-03-02 23:24 Michael Weber
2015-08-11 14:15 Michael Weber
2015-08-10 21:38 Sergei Trofimovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1593522476.77e589717e3fe5788ef0030d5cc4a2517670cc9a.mjo@gentoo \
--to=mjo@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox