From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/genkernel:master commit in: gkbuilds/
Date: Tue, 6 Jul 2021 18:07:58 +0000 (UTC) [thread overview]
Message-ID: <1625592292.9da63337a5462a8a75a4afe0f09051dcf23aeac8.whissi@gentoo> (raw)
commit: 9da63337a5462a8a75a4afe0f09051dcf23aeac8
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 6 17:24:52 2021 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Tue Jul 6 17:24:52 2021 +0000
URL: https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=9da63337
boost-build: Use BUILD CXX
When doing cross compile, the b2 program must be executable
on host system which tries to build boost.
Fixes: 5e340654 ("Bump boost to v1.76.0")
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
gkbuilds/boost-build.gkbuild | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gkbuilds/boost-build.gkbuild b/gkbuilds/boost-build.gkbuild
index 5d470c1..03d1f88 100644
--- a/gkbuilds/boost-build.gkbuild
+++ b/gkbuilds/boost-build.gkbuild
@@ -12,10 +12,12 @@ QA_IGNORE_DYNAMICALLY_LINKED_PROGRAM='(bjam|b2)$'
src_compile() {
cd engine || die "Failed to chdir to '${S}/engine'!"
+ # Using BUILD CXX here because the host system
+ # building the initramfs must be able to execute created b2 program
local myargs=(
./build.sh
cxx
- --cxx="$(tc-getCXX)"
+ --cxx="$(tc-getBUILD_CXX)"
--cxxflags="${CXXFLAGS}"
-d+2
--without-python
next reply other threads:[~2021-07-06 18:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 18:07 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-23 19:12 [gentoo-commits] proj/genkernel:master commit in: gkbuilds/ Ben Kohler
2024-05-22 14:59 Ben Kohler
2024-05-03 17:10 Ben Kohler
2024-04-29 17:26 Ben Kohler
2024-04-29 17:13 Ben Kohler
2024-04-29 17:13 Ben Kohler
2024-04-29 16:20 Ben Kohler
2024-04-29 16:20 Ben Kohler
2024-04-29 15:42 Ben Kohler
2024-04-27 13:55 Ben Kohler
2023-07-05 20:41 Sam James
2022-07-04 4:48 Robin H. Johnson
2022-05-16 5:34 Robin H. Johnson
2022-05-16 5:34 Robin H. Johnson
2021-11-15 18:32 Thomas Deutschmann
2021-11-15 18:32 Thomas Deutschmann
2021-10-01 18:44 Thomas Deutschmann
2021-03-15 20:02 Thomas Deutschmann
2021-02-18 13:32 Thomas Deutschmann
2021-02-18 13:32 Thomas Deutschmann
2021-02-08 22:10 Thomas Deutschmann
2020-08-28 20:18 Thomas Deutschmann
2020-08-28 20:18 Thomas Deutschmann
2020-08-28 20:18 Thomas Deutschmann
2020-08-27 17:53 Thomas Deutschmann
2020-08-25 16:48 Thomas Deutschmann
2020-08-19 1:14 Thomas Deutschmann
2020-07-23 23:57 Thomas Deutschmann
2020-07-21 0:23 Thomas Deutschmann
2020-07-16 15:03 Thomas Deutschmann
2020-07-16 15:03 Thomas Deutschmann
2020-07-16 15:03 Thomas Deutschmann
2020-07-16 15:03 Thomas Deutschmann
2020-06-20 2:17 Thomas Deutschmann
2020-06-16 13:53 Thomas Deutschmann
2020-06-16 13:53 Thomas Deutschmann
2020-05-14 21:56 Thomas Deutschmann
2020-04-07 23:03 Thomas Deutschmann
2020-02-15 21:08 Thomas Deutschmann
2020-02-15 21:08 Thomas Deutschmann
2019-12-31 2:41 Thomas Deutschmann
2019-12-14 0:26 Thomas Deutschmann
2019-11-25 15:02 Thomas Deutschmann
2019-10-02 22:45 Thomas Deutschmann
2019-09-01 20:35 Thomas Deutschmann
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=1625592292.9da63337a5462a8a75a4afe0f09051dcf23aeac8.whissi@gentoo \
--to=whissi@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