From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4
Date: Mon, 28 Nov 2022 12:42:38 +0100 [thread overview]
Message-ID: <2732MR.ANT1XFWZ05B13@t-online.de> (raw)
In-Reply-To: <CANNYZj9OzcCqoC9=cDcMVPDc85KZbuWuksekUgg0YhDWsG+TrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Am Mo, 28. Nov 2022 um 12:28:31 +0100 schrieb Alexander Kanavin
<alex.kanavin@gmail.com>:
> This needs to be explained. And we need to find a better way to do it,
> preferably one that is acceptable upstream.
Now thats somehow problematic. I had this issue also with seahorse,
that wants to know at build time what targets ssh-keygen path would be.
We need a way to look for the targets ssh binary paths but since
openssh for whatever reason doesn't support pkgconfig i guess we are
forced to hack it.
Another possibility would be to add an openssh-native recipe. I sent a
patch for that but it was rejected for valid reasons.
[-- Attachment #2: Type: text/html, Size: 818 bytes --]
next prev parent reply other threads:[~2022-11-28 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:22 [oe-core][PATCHv2] gcr: add recipe for gcr-4, needed to build with gtk4 Markus Volk
2022-11-28 11:25 ` Markus Volk
2022-11-28 11:28 ` Alexander Kanavin
2022-11-28 11:42 ` Markus Volk [this message]
2022-11-28 11:45 ` Alexander Kanavin
2022-11-28 12:07 ` Markus Volk
2022-11-28 13:13 ` Alexander Kanavin
2022-11-28 13:34 ` Markus Volk
[not found] ` <172BBC1E4D879E7E.11309@lists.openembedded.org>
2022-11-28 11:32 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 12:27 Markus Volk
2022-11-27 19:11 ` Alexandre Belloni
2022-11-27 19:38 ` Markus Volk
2022-11-27 20:35 ` Alexander Kanavin
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=2732MR.ANT1XFWZ05B13@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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