public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/bpf-toolchain/
Date: Fri, 16 Aug 2024 00:39:16 +0000 (UTC)	[thread overview]
Message-ID: <1723768739.536102c0b42ff966ac4e37e19b0f60ad6e90ddec.sam@gentoo> (raw)

commit:     536102c0b42ff966ac4e37e19b0f60ad6e90ddec
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Aug 16 00:37:48 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Aug 16 00:38:59 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=536102c0

sys-devel/bpf-toolchain: drop obsolete comment

I copied this comment from mingw64-toolchain and was waiting for
builds to finish on a few machines to see if it made any difference
before updating the number and apparently it.. barely does?

I'll come back to it another time in case I'm missing something though.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-devel/bpf-toolchain/bpf-toolchain-14.2.0-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-devel/bpf-toolchain/bpf-toolchain-14.2.0-r2.ebuild b/sys-devel/bpf-toolchain/bpf-toolchain-14.2.0-r2.ebuild
index ddd76d00070c..dfd388189afa 100644
--- a/sys-devel/bpf-toolchain/bpf-toolchain-14.2.0-r2.ebuild
+++ b/sys-devel/bpf-toolchain/bpf-toolchain-14.2.0-r2.ebuild
@@ -198,7 +198,7 @@ src_compile() {
 	# and it can lead to .a mangling, notably with 32bit (breaks toolchain)
 	dostrip -x ${bpftdir}/{${CTARGET}/lib{,32},lib/gcc/${CTARGET}}
 
-	# ... and instead do it here given this saves ~60MB
+	# TODO: Check if this is worth doing, it may not be
 	if use strip; then
 		einfo "Stripping ${CTARGET} static libraries ..."
 		find "${sysroot}"/{,lib/gcc/}${CTARGET} -type f -name '*.a' \


             reply	other threads:[~2024-08-16  0:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  0:39 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-26 15:30 [gentoo-commits] repo/gentoo:master commit in: sys-devel/bpf-toolchain/ Arthur Zamarin
2025-04-26  6:00 Sam James
2025-04-26  6:00 Sam James
2025-04-25 18:17 Sam James
2025-04-11 16:05 Sam James
2025-03-08 11:07 Sam James
2025-01-05 13:40 WANG Xuerui
2024-12-09 12:36 Arthur Zamarin
2024-11-02 10:00 Arthur Zamarin
2024-09-12 14:58 Sam James
2024-09-09 20:44 Arthur Zamarin
2024-09-09 13:46 Sam James
2024-09-08 21:59 Sam James
2024-08-31  6:39 Sam James
2024-08-23 13:00 Arthur Zamarin
2024-08-20 19:00 Sam James
2024-08-19 19:22 Sam James
2024-08-19 17:33 Sam James
2024-08-19 17:33 Sam James
2024-08-19 13:50 Jakov Smolić
2024-08-19 12:40 Arthur Zamarin
2024-08-19 12:40 Arthur Zamarin
2024-08-19 10:51 Arthur Zamarin
2024-08-19 10:44 Arthur Zamarin
2024-08-19  8:42 Sam James
2024-08-15 23:47 Sam James
2024-08-15 23:47 Sam James
2024-08-15 22:18 Sam James
2024-08-07  2:53 Sam James

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=1723768739.536102c0b42ff966ac4e37e19b0f60ad6e90ddec.sam@gentoo \
    --to=sam@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