From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Build options leak when building a target's dependency.
Date: Sat, 26 Dec 2020 20:28:37 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27456@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3169 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/27456
Description:
My test case is with `efl` and `enlightenment`; to reproduce, you simply need to increase the revision in both packages, then try to build *enlightenment*, with `./xbps-src pkg enlightenment`. When it doesn't find the up to date `efl` dependency, it will attempt to build it, and fail, as seen here:
```
=> xbps-src: updating repositories for host (x86_64)...
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/current/x86_64-repodata' ...
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://mirror.clarkson.edu/voidlinux/current/debug/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> enlightenment-0.24.2_1: removing autodeps, please wait...
=> enlightenment-0.24.2_1: the following build options are set:
wayland: Enable support for the Wayland backend (ON)
=> enlightenment-0.24.2_1: building [meson] for x86_64...
[host] efl-1.24.4_1: not found
[host] pkg-config-0.29.2_2: found (https://mirror.clarkson.edu/voidlinux/current)
[host] gettext-0.21_2: found (https://mirror.clarkson.edu/voidlinux/current)
[host] xorg-server-xwayland-1.20.10_2: found (https://mirror.clarkson.edu/voidlinux/current)
[host] meson-0.55.3_3: found (https://mirror.clarkson.edu/voidlinux/current)
[target] gettext-devel-0.21_2: found (https://mirror.clarkson.edu/voidlinux/current)
[target] efl-devel-1.24.4_1: not found
[target] pam-devel-1.3.0_2: found (https://mirror.clarkson.edu/voidlinux/current)
[target] xkeyboard-config-2.31_1: found (https://mirror.clarkson.edu/voidlinux/current)
[target] libxkbcommon-devel-1.0.3_1: found (https://mirror.clarkson.edu/voidlinux/current)
[target] MesaLib-devel-20.3.1_1: found (https://mirror.clarkson.edu/voidlinux/current)
[target] wayland-devel-1.18.0_3: found (https://mirror.clarkson.edu/voidlinux/current)
[runtime] desktop-file-utils-0.26_1: found (https://mirror.clarkson.edu/voidlinux/current)
[runtime] hicolor-icon-theme-0.17_3: found (https://mirror.clarkson.edu/voidlinux/current)
[runtime] xkeyboard-config-2.31_1: found (https://mirror.clarkson.edu/voidlinux/current)
[runtime] xorg-server-xwayland-1.20.10_2: found (https://mirror.clarkson.edu/voidlinux/current)
[runtime] efl-devel-1.24.4_1: not found
=> ERROR: efl-1.24.4_1: cannot be built, it's currently broken; see the build log:
=> ERROR: efl-1.24.4_1: wayland requires drm
```
I assume this happens because `enlightenment` has `build_options_default=wayland`, while `efl` has `build_options_default="elogind harfbuzz pulseaudio gstreamer x11 wayland opengl gles2 drm glib ibus"`. `efl`'s options are overridden, and we (luckily) get an error, because the `wayland` build option requires `drm`.
next reply other threads:[~2020-12-26 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 19:28 ericonr [this message]
2020-12-27 21:38 ` fosslinux
2021-08-12 21:58 ` ericonr
2021-08-12 22:02 ` Duncaen
2022-05-01 2:14 ` github-actions
2022-05-01 19:05 ` ericonr
2022-07-31 2:13 ` github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27456@inbox.vuxu.org \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).