public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: multilib@gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH multilib-build] Add multilib_is_native_abi() helper.
Date: Sat, 29 Jun 2013 10:35:45 +0200	[thread overview]
Message-ID: <1372494945-19681-1-git-send-email-mgorny@gentoo.org> (raw)

We've been so far inlining the snippet into ebuilds. This meant that
some people didn't know how to do this, some more did it improperly and
in the end -- if it failed not good enough -- changing it will require
changing all the ebuilds.
---
 gx86/eclass/multilib-build.eclass | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/gx86/eclass/multilib-build.eclass b/gx86/eclass/multilib-build.eclass
index a4b7c01..22a471e 100644
--- a/gx86/eclass/multilib-build.eclass
+++ b/gx86/eclass/multilib-build.eclass
@@ -338,5 +338,21 @@ multilib_install_wrappers() {
 	fi
 }
 
+# @FUNCTION: multilib_is_native_abi
+# @DESCRIPTION:
+# Determine whether the currently built ABI is the profile native.
+# Return true status (0) if that is true, otherwise false (1).
+#
+# This is often useful for configure calls when some of the options are
+# supposed to be disabled for multilib ABIs (like those used for
+# executables only).
+multilib_is_native_abi() {
+	debug-print-function ${FUNCNAME} "${@}"
+
+	[[ ${#} -eq 0 ]] || die "${FUNCNAME}: too many arguments"
+
+	[[ ${ABI} == ${DEFAULT_ABI} ]]
+}
+
 _MULTILIB_BUILD=1
 fi
-- 
1.8.2.1



             reply	other threads:[~2013-06-29  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29  8:35 Michał Górny [this message]
2013-06-29 10:52 ` [gentoo-dev] [PATCH multilib-build] Add multilib_is_native_abi() helper Michael Weber
2013-06-29 11:04   ` Michael Weber
2013-06-29 19:47 ` Alexis Ballier

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=1372494945-19681-1-git-send-email-mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=multilib@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