public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: scripts/
Date: Sun, 29 Mar 2020 17:45:24 +0000 (UTC)	[thread overview]
Message-ID: <1585503879.772775deadb874bde912cfaa7e1252f40631f741.mattst88@gentoo> (raw)

commit:     772775deadb874bde912cfaa7e1252f40631f741
Author:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 29 17:26:26 2020 +0000
Commit:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sun Mar 29 17:44:39 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=772775de

scripts/bootstrap.sh: Remove nptlonly cruft

Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>

 scripts/bootstrap.sh | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/scripts/bootstrap.sh b/scripts/bootstrap.sh
index 0a4bc06c3c8..aa31fb15e8b 100755
--- a/scripts/bootstrap.sh
+++ b/scripts/bootstrap.sh
@@ -239,9 +239,6 @@ for opt in ${ORIGUSE} ; do
 			fi
 			USE_NPTL=1
 			;;
-		nptlonly)
-			USE_NPTLONLY=1
-			;;
 		multilib)
 			ALLOWED_USE="${ALLOWED_USE} multilib"
 			;;
@@ -284,13 +281,10 @@ for atom in portage.settings.packages:
 # Do we really want gettext/nls?
 [[ ${USE_NLS} != 1 ]] && myGETTEXT=
 
-# Do we really have no 2.4.x nptl kernels in portage?
 if [[ ${USE_NPTL} = "1" ]] ; then
 	myOS_HEADERS="$(portageq best_visible / '>=sys-kernel/linux-headers-2.6.0')"
 	[[ -n ${myOS_HEADERS} ]] && myOS_HEADERS=">=${myOS_HEADERS}"
 	ALLOWED_USE="${ALLOWED_USE} nptl"
-	# Should we build with nptl only?
-	[[ ${USE_NPTLONLY} = "1" ]] && ALLOWED_USE="${ALLOWED_USE} nptlonly"
 fi
 [[ -z ${myOS_HEADERS} ]] && myOS_HEADERS="$(portageq expand_virtual / virtual/os-headers)"
 


             reply	other threads:[~2020-03-29 17:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 17:45 Matt Turner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-12 11:08 [gentoo-commits] repo/gentoo:master commit in: scripts/ Sam James
2024-01-12 11:08 Sam James
2024-01-12 11:08 Sam James
2023-10-02  3:25 Joshua Kinard
2023-02-22 16:21 Sam James
2022-04-19 21:17 Mike Gilbert
2022-04-19 21:12 Mike Gilbert
2021-09-02 10:58 Ulrich Müller
2020-06-07 13:15 Ulrich Müller
2020-03-30  1:37 Matt Turner
2020-03-29 17:45 Matt Turner
2020-03-29 17:45 Matt Turner
2020-03-29 17:45 Matt Turner
2020-01-19  5:08 Zac Medico
2020-01-19  4:39 Zac Medico
2017-03-04 18:11 Jorge Manuel B. S. Vicetto
2017-03-04 18:11 Jorge Manuel B. S. Vicetto

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=1585503879.772775deadb874bde912cfaa7e1252f40631f741.mattst88@gentoo \
    --to=mattst88@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