public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/b2/
Date: Fri,  2 Dec 2022 21:32:47 +0000 (UTC)	[thread overview]
Message-ID: <1670016761.a7764bed64842d82a4bcfa787c2d60896c20d269.soap@gentoo> (raw)

commit:     a7764bed64842d82a4bcfa787c2d60896c20d269
Author:     David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Fri Dec  2 21:32:41 2022 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Fri Dec  2 21:32:41 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7764bed

dev-util/b2: add 4.9.3

Signed-off-by: David Seifert <soap <AT> gentoo.org>

 dev-util/b2/Manifest        |  1 +
 dev-util/b2/b2-4.9.3.ebuild | 66 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 67 insertions(+)

diff --git a/dev-util/b2/Manifest b/dev-util/b2/Manifest
index 1879967af9e4..488992304be3 100644
--- a/dev-util/b2/Manifest
+++ b/dev-util/b2/Manifest
@@ -1 +1,2 @@
 DIST b2-4.9.2.tar.gz 975882 BLAKE2B 83c2ef85c9f1ae20922541ca8c344316f1660ee069426e3a9907c0a19e1c94db470c67d0c29a1f31788eddb86ab414ab06b9713f8ea53d974d1d8f0ca29f4aa5 SHA512 eab180770608b863dcf6a5fbc626e1733cf4353cf62f4189bd28258a03591fdb7853f5dddb4d3dad60f1bb06db5415025b792a30c2c65f7b1278f61e33f903e3
+DIST b2-4.9.3.tar.gz 975934 BLAKE2B 8d16e7227676786408f0d84efb577806e304a9181b89656dad1243b5b0b48e67d4226fa51ea97d4ea10110e4ea86f3ae2884d711fa4b04e36bdaa68dff0a4710 SHA512 8f861074a50720ad5469277a469523ef5f87ef2aab65d745f4c5e6af0ed8f40af91c43cd42b7845982c065974026ce1ecc77a831cd0c698c7e22fa848cc81009

diff --git a/dev-util/b2/b2-4.9.3.ebuild b/dev-util/b2/b2-4.9.3.ebuild
new file mode 100644
index 000000000000..f1a5c248ac6c
--- /dev/null
+++ b/dev-util/b2/b2-4.9.3.ebuild
@@ -0,0 +1,66 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit edo flag-o-matic toolchain-funcs
+
+MY_PV="$(ver_rs 1- _)"
+
+DESCRIPTION="A system for large project software construction, simple to use and powerful"
+HOMEPAGE="https://www.bfgroup.xyz/b2/"
+SRC_URI="https://github.com/bfgroup/b2/archive/refs/tags/${PV}.tar.gz -> ${P}.tar.gz"
+S="${WORKDIR}/${P}/src"
+
+LICENSE="Boost-1.0"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+IUSE="examples"
+RESTRICT="test"
+
+RDEPEND="!dev-util/boost-build"
+
+PATCHES=(
+	"${FILESDIR}"/${PN}-4.9.2-disable_python_rpath.patch
+	"${FILESDIR}"/${PN}-4.9.2-darwin-gentoo-toolchain.patch
+	"${FILESDIR}"/${PN}-4.9.2-add-none-feature-options.patch
+	"${FILESDIR}"/${PN}-4.9.2-no-implicit-march-flags.patch
+	"${FILESDIR}"/${PN}-4.9.2-odr.patch
+)
+
+src_configure() {
+	# need to enable LFS explicitly for 64-bit offsets on 32-bit hosts (#761100)
+	append-lfs-flags
+}
+
+src_compile() {
+	cd engine || die
+
+	# upstream doesn't want separate flags for CPPFLAGS/LDFLAGS
+	# https://github.com/bfgroup/b2/pull/187#issuecomment-1335688424
+	edo ${CONFIG_SHELL:-${BASH}} ./build.sh cxx --cxx="$(tc-getCXX)" --cxxflags="${CXXFLAGS} ${CPPFLAGS} ${LDFLAGS}" -d+2 --without-python
+}
+
+src_test() {
+	# Forget tests, b2 is a lost cause
+	:
+}
+
+src_install() {
+	dobin engine/b2
+
+	insinto /usr/share/b2/src
+	doins -r "${FILESDIR}/site-config.jam" \
+		bootstrap.jam build-system.jam ../example/user-config.jam \
+		build kernel options tools util
+
+	find "${ED}"/usr/share/b2/src -iname '*.py' -delete || die
+
+	dodoc ../notes/{changes,release_procedure,build_dir_option,relative_source_paths}.txt
+
+	if use examples; then
+		docinto examples
+		dodoc -r ../example/.
+		docompress -x /usr/share/doc/${PF}/examples
+	fi
+}


             reply	other threads:[~2022-12-02 21:32 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 21:32 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-11 14:11 [gentoo-commits] repo/gentoo:master commit in: dev-util/b2/ David Seifert
2023-08-23  9:02 David Seifert
2023-08-21 11:25 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-08-21 11:08 Sam James
2023-07-22 12:15 David Seifert
2023-07-16 10:32 David Seifert
2023-06-19 18:10 David Seifert
2023-04-14 23:12 David Seifert
2023-04-14 22:19 Sam James
2023-04-14 21:10 Sam James
2023-04-14 21:10 Sam James
2023-04-14 21:10 Sam James
2023-04-14 21:10 Sam James
2023-04-14 21:10 Sam James
2023-04-14 21:05 Arthur Zamarin
2023-04-14 21:05 Arthur Zamarin
2023-03-25 11:03 David Seifert
2023-03-11 19:15 David Seifert
2023-02-20 13:49 Sam James
2023-01-21 19:41 Arthur Zamarin
2023-01-17 19:52 Arthur Zamarin
2022-12-02 18:47 Arthur Zamarin
2022-11-23  2:26 Sam James
2022-11-21 20:43 Arthur Zamarin
2022-11-21 17:52 Arthur Zamarin
2022-11-21 17:52 Arthur Zamarin
2022-11-21 17:52 Arthur Zamarin
2022-11-21 17:50 Arthur Zamarin
2022-11-21 17:43 Arthur Zamarin
2022-09-09  9:41 Sam James
2022-09-04 11:20 David Seifert

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=1670016761.a7764bed64842d82a4bcfa787c2d60896c20d269.soap@gentoo \
    --to=soap@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