From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 49437@debbugs.gnu.org
Subject: [bug#49437] [PATCH core-updates] build-system/qt: Fix build failures when
Date: Wed, 22 Sep 2021 23:53:20 -0400 [thread overview]
Message-ID: <87bl4kkkwf.fsf_-_@gmail.com> (raw)
In-Reply-To: <f6c38c054ffdec02b446f21eb8abe5d471a0910b.camel@telenet.be> (Maxime Devos's message of "Thu, 08 Jul 2021 22:59:08 +0200")
Hello,
Maxime Devos <maximedevos@telenet.be> writes:
> Mathieu Othacehe schreef op do 08-07-2021 om 21:37 [+0200]:
>> Hey,
>>
>> > One of the features of 'qt-build-system' is that it automatically
>> > creates wrappers, but it needs 'bash' (or 'bash-minimal') to do
>> > so. If "bin/bash" doesn't exist among the 'inputs', then
>> > 'search-input-file' (used by 'wrap-all-programs') will raise an
>> > exception. Address this exception by adding "bash-minimal" to
>> > 'host-inputs' when cross-compiling.
>>
>> I'd like to test it but it looks like qt-build-system drags glib which
>> uses the meson-build-system that doesn't support cross-compilation.
>>
>> Did you test this patch, on top of your meson series?
>
> I had started "./pre-inst-env guix build qtsvg" but that's no
> cross-compilation. I'll rebase the meson series and test it!
Did it test fine?
Thanks,
Maxim
next prev parent reply other threads:[~2021-09-23 3:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:25 [bug#49437] [PATCH core-updates] build-system/qt: Fix build failures when Maxime Devos
2021-07-08 14:45 ` Mathieu Othacehe
2021-07-08 17:51 ` Maxime Devos
2021-07-08 19:37 ` Mathieu Othacehe
2021-07-08 20:59 ` Maxime Devos
2021-09-23 3:53 ` Maxim Cournoyer [this message]
2021-10-03 8:56 ` Maxime Devos
2023-03-29 2:15 ` Maxim Cournoyer
2023-04-04 18:59 ` Maxime Devos
2023-04-07 21:15 ` Maxim Cournoyer
2024-01-20 21:11 ` bug#49437: " Maxim Cournoyer
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=87bl4kkkwf.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=49437@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.