PING!
Attached again. (this time, the diff should cleanly apply, sorry about
it if it didn't cleanly apply before)
Appreciated-
--
iz (she/her)
> i like to say mundane things,
> there are too many uninteresting things
> that go unnoticed.
izder456 (dot) neocities (dot) org
diff --git games/cl
On Sat, Jan 04, 2025 at 12:15:07AM -0600, izzy Meyer wrote:
> On Sun, 22 Dec 2024 19:55:46 -0600
> izzy Meyer wrote:
> > Ping!
> > Attached again
This doesn't build. The new patch for Logger.c doesn't apply.
--Kurt
On Sun, 22 Dec 2024 19:55:46 -0600
izzy Meyer wrote:
> Ping!
>
> Attached again
>
Attached again. Any committers?
--
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 Makefile Makefile
Ping!
Attached again
--
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 Makefile Makefile
index ff38e16fe..3137a1d09 100644
--- Makefile
+++ Makefile
@@ -3,10 +3,10 @@ BROKEN-sparc64 = .
On Sat, 23 Nov 2024 21:59:00 -0600
izzy Meyer wrote:
> > > > > > Hello ports@!
> > > > > >
> > > > > > PING!
> > > > > >
> > > > > > Turns out OpenBSD uses backtrace from -lexecinfo and
> > > > > > upstream introduced a bug before releasing 1.3.7 that
> > > > > > unintentionally broke -lexecinf
On Sun, 17 Nov 2024 13:45:14 -0600
izzy Meyer wrote:
> On Sat, 16 Nov 2024 15:23:12 -0500
> Thomas Frohwein wrote:
>
> > On Wed, 13 Nov 2024 18:16:28 -0600
> > izzy Meyer wrote:
> >
> > > On Fri, 25 Oct 2024 12:22:18 -0500
> > > izzy Meyer wrote:
> > >
> > > > On Tue, 15 Oct 2024 16:2
On Sat, 16 Nov 2024 15:23:12 -0500
Thomas Frohwein wrote:
> On Wed, 13 Nov 2024 18:16:28 -0600
> izzy Meyer wrote:
>
> > On Fri, 25 Oct 2024 12:22:18 -0500
> > izzy Meyer wrote:
> >
> > > On Tue, 15 Oct 2024 16:28:16 -0500
> > > izzy Meyer wrote:
> > >
> > > > Hello ports@!
> > > >
> >
On Wed, 13 Nov 2024 18:16:28 -0600
izzy Meyer wrote:
> On Fri, 25 Oct 2024 12:22:18 -0500
> izzy Meyer wrote:
>
> > On Tue, 15 Oct 2024 16:28:16 -0500
> > izzy Meyer wrote:
> >
> > > Hello ports@!
> > >
> > > PING!
> > >
> > > Turns out OpenBSD uses backtrace from -lexecinfo and upstream
>
On Fri, 25 Oct 2024 12:22:18 -0500
izzy Meyer wrote:
> On Tue, 15 Oct 2024 16:28:16 -0500
> izzy Meyer wrote:
>
> > Hello ports@!
> >
> > PING!
> >
> > Turns out OpenBSD uses backtrace from -lexecinfo and upstream
> > introduced a bug before releasing 1.3.7 that unintentionally broke
> > -lex
On Tue, 15 Oct 2024 16:28:16 -0500
izzy Meyer wrote:
> Hello ports@!
>
> PING!
>
> Turns out OpenBSD uses backtrace from -lexecinfo and upstream
> introduced a bug before releasing 1.3.7 that unintentionally broke
> -lexecinfo linking on OpenBSD targets.
>
> After a little back-and-forth with
On Tue, 15 Oct 2024 23:06:15 +0100
Stuart Henderson wrote:
>
> I haven't been following this (and don't really do games on OpenBSD
> apart the occasional bit of xonix). But AFAIK the backtrace functions
> (in libexecinfo on OpenBSD and IIRC FreeBSD, and glibc on Linux)
> aren't expected to requir
On 2024/10/15 16:28, izzy Meyer wrote:
> After a little back-and-forth with the dev on discord as well as in a
> GitHub PR, we decided to merge a new patch that introduces a LINK
> variable in the Makefile to future proof other platforms who may not
> link to _Unwind correctly out of the gate to ma
Hello ports@!
PING!
Turns out OpenBSD uses backtrace from -lexecinfo and upstream
introduced a bug before releasing 1.3.7 that unintentionally broke
-lexecinfo linking on OpenBSD targets.
After a little back-and-forth with the dev on discord as well as in a
GitHub PR, we decided to merge a new p
On Mon, 14 Oct 2024 01:38:07 +0200
Kirill A. Korinsky wrote:
> I really doubt that this changes break anything. I don't see any harm
> from linking c program by c++ compiler / linker.
I was only suspecting it may break things, as this program supports
very old versions of compilers, on deprecate
On Mon, 14 Oct 2024 01:28:30 +0200,
izzy Meyer wrote:
>
> AH! right that makes sense. I wonder if we can have a platform-specific
> patch upstreamed so the CXX over CC pr doesn't break things on other
> platforms. (they support many!)
>
I really doubt that this changes break anything. I don't s
On Mon, 14 Oct 2024 01:13:53 +0200
Kirill A. Korinsky wrote:
> On Mon, 14 Oct 2024 00:59:29 +0200,
> izzy Meyer wrote:
> >
> > I'll send that makefile patch upstream. Did you see my recent reply
> > that upstream fixed things?
> >
>
> I did, they simple disabled using this on OpenBSD. I not su
On Mon, 14 Oct 2024 00:59:29 +0200,
izzy Meyer wrote:
>
> I'll send that makefile patch upstream. Did you see my recent reply
> that upstream fixed things?
>
I did, they simple disabled using this on OpenBSD. I not sure, but if
upstream goes that way the list of platforms where it is disabled wi
On Sun, 13 Oct 2024 17:59:29 -0500
izzy Meyer wrote:
> On Sun, 13 Oct 2024 23:56:55 +0200
> Kirill A. Korinsky wrote:
>
> > On Sun, 13 Oct 2024 21:50:06 +0200,
> > izzy Meyer wrote:
> > >
> > > ld: error: undefined symbol: _Unwind_Backtrace
> > > >>> referenced by Logger.c:1363 (src/Logger.c:
On Sun, 13 Oct 2024 23:56:55 +0200
Kirill A. Korinsky wrote:
> On Sun, 13 Oct 2024 21:50:06 +0200,
> izzy Meyer wrote:
> >
> > ld: error: undefined symbol: _Unwind_Backtrace
> > >>> referenced by Logger.c:1363 (src/Logger.c:1363)
> > >>> build-openbsd/Logger.o:(Logger_Backtrace)
>
On Sun, 13 Oct 2024 21:50:06 +0200,
izzy Meyer wrote:
>
> ld: error: undefined symbol: _Unwind_Backtrace
> >>> referenced by Logger.c:1363 (src/Logger.c:1363)
> >>> build-openbsd/Logger.o:(Logger_Backtrace)
>
> ld: error: undefined symbol: _Unwind_GetIP
> >>> referenced by Logger.
On Sun, 13 Oct 2024 14:50:06 -0500
izzy Meyer wrote:
> On Sun, 13 Oct 2024 14:35:29 -0500
> izzy Meyer wrote:
>
> > Hey ports@
> >
> > This is an update to 1.3.7, everything works, but for now needs to
> > be built with gcc as upstream changed some stuff with libunwind,
> > which breaks clang
On Sun, 13 Oct 2024 14:35:29 -0500
izzy Meyer wrote:
> Hey ports@
>
> This is an update to 1.3.7, everything works, but for now needs to be
> built with gcc as upstream changed some stuff with libunwind, which
> breaks clang compat.
>
> I am working with upstream in their discord to get clang s
Hey ports@
This is an update to 1.3.7, everything works, but for now needs to be
built with gcc as upstream changed some stuff with libunwind, which
breaks clang compat.
I am working with upstream in their discord to get clang supported. I
am not a very good C dev so IDK where to start.
Diff is
23 matches
Mail list logo
