From: Arve Barsnes <arve.barsnes@gmail.com>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Yet another USE flag problem
Date: Mon, 4 Jan 2021 13:39:47 +0100 [thread overview]
Message-ID: <CAJjrzcWoD3ONjThb-N7KQObnbSg7CCYXNbn4c73LX28u9hv8Jg@mail.gmail.com> (raw)
In-Reply-To: <20210104121523.ympjqtjiee2cm5ku@becker.bs.l>
On Mon, 4 Jan 2021 at 13:15, Bertram Scharpf <lists@bertram-scharpf.de> wrote:
> # grep -rnHi lua /etc/portage
> /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit
> /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit
> /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit
> /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit
> /etc/portage/package.accept_keywords/local:26:<dev-lang/lua-5.2 ~amd64
>
> Here's another time how emerge complains:
>
> - app-editors/neovim-0.4.4-r100::gentoo (Change USE: -lua_single_target_lua5-1, this change violates use flag constraints defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 )')
>
> As far as I understand this, emerge tells me to remove the
> use flag "lua_single_target_lua5-1" because the use flag
> "lua_single_target_lua5-1" is required.
As far as I understand it, this is saying that your emerge command is
about to remove that USE flag from neovim, which breaks the
constraint. So basically some other package is stopping your update.
Your original mail mentioned that this was because of dev-lua/luv. You
have in your /etc/portage/package.use/zz-autouse set the luajit flag
on this package. Might this be the problem?
I'm not that familiar with lua, but as far as I understand the output,
app-editors/neovim and dev-lua/luv needs the same LUA_SINGLE_TARGET,
and setting that USE flag on dev-lua/luv might trip up this. Reading
the latest ebuild, this flag has been removed in the ~amd64 package,
so might as well remove it now and see if that fixes your problem.
Regards,
Arve
next prev parent reply other threads:[~2021-01-04 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:05 [gentoo-user] Yet another USE flag problem Bertram Scharpf
2021-01-04 6:09 ` Arve Barsnes
2021-01-04 12:15 ` Bertram Scharpf
2021-01-04 12:39 ` Arve Barsnes [this message]
2021-01-04 13:46 ` Bertram Scharpf
2021-01-04 14:12 ` Arve Barsnes
2021-01-04 15:17 ` Bertram Scharpf
2021-01-04 15:12 ` Daniel Frey
2021-01-04 15:32 ` Bertram Scharpf
2021-01-05 2:42 ` Daniel Frey
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=CAJjrzcWoD3ONjThb-N7KQObnbSg7CCYXNbn4c73LX28u9hv8Jg@mail.gmail.com \
--to=arve.barsnes@gmail.com \
--cc=gentoo-user@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