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: dev-lang/tcc/
Date: Mon, 25 Oct 2021 12:38:45 +0000 (UTC)	[thread overview]
Message-ID: <1635165503.1adaddf5110adeaf1e3b84d1d15d42e66798c4ef.sam@gentoo> (raw)

commit:     1adaddf5110adeaf1e3b84d1d15d42e66798c4ef
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 25 12:38:23 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Oct 25 12:38:23 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1adaddf5

dev-lang/tcc: add musl/uclibc support

Closes: https://bugs.gentoo.org/765652
Bug: https://bugs.gentoo.org/715428
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-lang/tcc/tcc-0.9.27_p20211022.ebuild | 6 ++++++
 dev-lang/tcc/tcc-9999.ebuild             | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/dev-lang/tcc/tcc-0.9.27_p20211022.ebuild b/dev-lang/tcc/tcc-0.9.27_p20211022.ebuild
index f53743b5e6b..3081fc06884 100644
--- a/dev-lang/tcc/tcc-0.9.27_p20211022.ebuild
+++ b/dev-lang/tcc/tcc-0.9.27_p20211022.ebuild
@@ -51,11 +51,17 @@ src_prepare() {
 }
 
 src_configure() {
+	local libc
+
 	use test && unset CFLAGS LDFLAGS # Tests run with CC=tcc etc, they will fail hard otherwise
 					# better fixes welcome, it feels wrong to hack the env like this
 
+	use elibc_musl && libc=musl
+	use elibc_uclibc && libc=uClibc
+
 	# not autotools, so call configure directly
 	./configure --cc="$(tc-getCC)" \
+		${libc:+--config-${libc}} \
 		--prefix="${EPREFIX}/usr" \
 		--libdir="${EPREFIX}/usr/$(get_libdir)" \
 		--docdir="${EPREFIX}/usr/share/doc/${PF}"

diff --git a/dev-lang/tcc/tcc-9999.ebuild b/dev-lang/tcc/tcc-9999.ebuild
index f53743b5e6b..3081fc06884 100644
--- a/dev-lang/tcc/tcc-9999.ebuild
+++ b/dev-lang/tcc/tcc-9999.ebuild
@@ -51,11 +51,17 @@ src_prepare() {
 }
 
 src_configure() {
+	local libc
+
 	use test && unset CFLAGS LDFLAGS # Tests run with CC=tcc etc, they will fail hard otherwise
 					# better fixes welcome, it feels wrong to hack the env like this
 
+	use elibc_musl && libc=musl
+	use elibc_uclibc && libc=uClibc
+
 	# not autotools, so call configure directly
 	./configure --cc="$(tc-getCC)" \
+		${libc:+--config-${libc}} \
 		--prefix="${EPREFIX}/usr" \
 		--libdir="${EPREFIX}/usr/$(get_libdir)" \
 		--docdir="${EPREFIX}/usr/share/doc/${PF}"


             reply	other threads:[~2021-10-25 12:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 12:38 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-08 13:06 [gentoo-commits] repo/gentoo:master commit in: dev-lang/tcc/ Patrick Lauer
2024-03-17  8:42 Sam James
2023-03-03 19:46 Yixun Lan
2023-01-07 11:30 Arthur Zamarin
2023-01-04  0:28 Yixun Lan
2022-02-07  8:56 Yixun Lan
2022-02-07  8:56 Yixun Lan
2022-02-07  8:56 Yixun Lan
2021-10-25 13:01 Sam James
2021-10-25 13:01 Sam James
2021-10-25 12:35 Sam James
2020-02-14 22:40 Yixun Lan
2020-02-14 22:40 Yixun Lan
2019-04-11  4:10 Yixun Lan
2019-04-11  4:10 Yixun Lan
2019-04-09  3:14 Austin English
2018-05-13 19:20 Aaron Bauman
2017-12-18 21:11 Austin English
2017-12-18 21:11 Austin English
2016-06-02  4:40 Austin English

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=1635165503.1adaddf5110adeaf1e3b84d1d15d42e66798c4ef.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