Re: HOTFIX games/{bugdom,bugdom2,nanosaur,mightymike,ottomatic,billyfrontier} on sparc64
On Wed, 13 Mar 2024 19:07:07 +
> On March 13, 2024 7:24:26 PM GMT+01:00, Stuart Henderson via ports
>
> I think something like this would be preferable
>
> # requires C++20
> COMPILER = base-clang
>
I attached the diffs with this change
> > On 2024/03/13 19:36, Tobias Heider via ports wrote:
> >
> > but then you could also add ports clang and ports gcc right?
> > they should also support newer c++ versions
currently these ports use:
COMPILER = base-clang ports-gcc
yet they still fail on architectures without a C++20 compat compiler
afaik.
> > > "Stuart Henderson via ports" wrote:
> > > Could try it, but it seems fairly doubtful that they'll be good
> > > enough, c++20 support in gcc 8 was pretty limited (and uses
> > > -std=c++2a not -std=c++20), and ports-clang on base-gcc archs uses
> > > libestdc++ from gcc 8. (gcc/11 is in the ports tree but can't be
> > > used in bulks unless all c++ ports on whichever arch are switched
> > > from 8 to 11 otherwise there will be build conflicts).
This seems like the most reasonable fail-safe solution given the time
crunch. OK to merge?
--
-iz (they/them)
> i like to say mundane things,
> there are too many uninteresting things
> that go unnoticed.
izder456 (dot) neocities (dot) org
diff --git billyfrontier/Makefile billyfrontier/Makefile
index 5462bab38..9ba3101ff 100644
--- billyfrontier/Makefile
+++ billyfrontier/Makefile
@@ -18,7 +18,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
diff --git ottomatic/Makefile ottomatic/Makefile
index 55f9e5297..a250fbcaf 100644
--- ottomatic/Makefile
+++ ottomatic/Makefile
@@ -19,7 +19,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
diff --git mightymike/Makefile mightymike/Makefile
index 0149fc600..a6ec28fbe 100644
--- mightymike/Makefile
+++ mightymike/Makefile
@@ -18,7 +18,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
diff --git nanosaur/Makefile nanosaur/Makefile
index 96bcc0c6a..e8e9fd651 100644
--- nanosaur/Makefile
+++ nanosaur/Makefile
@@ -18,7 +18,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
diff --git bugdom2/Makefile bugdom2/Makefile
index 89dc4ad6f..eee36bbde 100644
--- bugdom2/Makefile
+++ bugdom2/Makefile
@@ -18,7 +18,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
diff --git bugdom/Makefile bugdom/Makefile
index f48f280f6..b6a8357fb 100644
--- bugdom/Makefile
+++ bugdom/Makefile
@@ -18,7 +18,7 @@ PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} GL SDL2 c m
# C++20
-COMPILER = base-clang ports-gcc
+COMPILER = base-clang
MODULES = devel/cmake
HOTFIX games/{bugdom,bugdom2,nanosaur,mightymike,ottomatic,billyfrontier} on sparc64
Hey ports@-
Looks like these ports I take MAINTAINER on fail on sparc64 with the
same u8string error, which AFAIK is a C++20 thing.
From what it looks like, sparc64 doesn't have a C++20 compiler, so they
unfortunately will be broken on that arch.
Attached are diffs that adds BROKEN-sparc64 to those ports.
Thanks.
--
-iz (they/them)
> i like to say mundane things,
> there are too many uninteresting things
> that go unnoticed.
izder456 (dot) neocities (dot) org
diff --git mightymike/Makefile mightymike/Makefile
index 0149fc600..49a2e3da7 100644
--- mightymike/Makefile
+++ mightymike/Makefile
@@ -6,6 +6,8 @@ DIST_TUPLE += github jorio MightyMike v${V} .
DIST_TUPLE += github jorio Pomme d57c28e205462e51063e787f9ebddaadff592f1e \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/mightymike
diff --git billyfrontier/Makefile billyfrontier/Makefile
index 5462bab38..14e686bb0 100644
--- billyfrontier/Makefile
+++ billyfrontier/Makefile
@@ -6,6 +6,8 @@ DIST_TUPLE += github jorio BillyFrontier v${V} .
DIST_TUPLE += github jorio Pomme 9fae17d7715314a3a20259ac2e87aa500a977695 \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/billy
diff --git ottomatic/Makefile ottomatic/Makefile
index 55f9e5297..090e15108 100644
--- ottomatic/Makefile
+++ ottomatic/Makefile
@@ -7,6 +7,8 @@ DIST_TUPLE += github jorio OttoMatic ${V} .
DIST_TUPLE += github jorio Pomme ef94150e2dcec522e3099f4d03a4e8f2639f7232 \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/otto
diff --git nanosaur/Makefile nanosaur/Makefile
index 96bcc0c6a..da0d75e85 100644
--- nanosaur/Makefile
+++ nanosaur/Makefile
@@ -6,6 +6,8 @@ DIST_TUPLE += github jorio Nanosaur v${V} .
DIST_TUPLE += github jorio Pomme d57c28e205462e51063e787f9ebddaadff592f1e \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/nano
diff --git bugdom2/Makefile bugdom2/Makefile
index 89dc4ad6f..ff6d86bfa 100644
--- bugdom2/Makefile
+++ bugdom2/Makefile
@@ -6,6 +6,8 @@ DIST_TUPLE += github jorio Bugdom2 v${V} .
DIST_TUPLE += github jorio Pomme c6a38eab19a11847024a13f9b3e2af0c2d908c3e \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/bug2
diff --git bugdom/Makefile bugdom/Makefile
index f48f280f6..ab17bd59a 100644
--- bugdom/Makefile
+++ bugdom/Makefile
@@ -6,6 +6,8 @@ DIST_TUPLE += github jorio Bugdom ${V} .
DIST_TUPLE += github jorio Pomme ef94150e2dcec522e3099f4d03a4e8f2639f7232 \
extern/Pomme
+BROKEN-sparc64 = needs C++20 compiler
+
CATEGORIES = games
HOMEPAGE = https://pangeasoft.net/bug
Question RE: Failed bulk build standard practice
Hey ports@- already messaged #openbsd about this on libera but for digital record's sake, I wanted to ask here as well. I take MAINTAINER on several ports with no ONLY_FOR_ARCH set. When looking through the bulk build reports in the ports@ lists this morning, I saw that some ports I worked on have failed on hardware I don't have access too. Is there a special practice we do when this occurrs, or is the port just never built into binary at release for that arch? is there something like a blacklist equivalent of ONLY_FOR_ARCH? also- If there isn't enough time to factor in these sort of hotfixes, what is general practice when RELEASE happens, and the ports are version froze in case I need to patch my port because someone on STABLE has experienced breakage? Still new-ish to this ports@ thing, forgive my noobiness :) Thanks, any guidance is much appreciated. -- -iz (they/them) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org
