Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2024 21:52:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 281257] base llvm csetjmp C++ header file now generates an error
Message-ID:  <bug-281257-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281257

            Bug ID: 281257
           Summary: base llvm csetjmp C++ header file now generates an
                    error
           Product: Base System
           Version: 14.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: misc
          Assignee: bugs@FreeBSD.org
          Reporter: bobf@mrp3.com
 Attachment #253310 text/plain
         mime type:

Created attachment 253310
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D253310&action=
=3Dedit
shar file for graphics/xaos containing patch

In 2 cases I have attempted to build ports using the latest llvm compiler t=
hat
comes with 14.1 RELEASE.

graphics/xaos
graphics/inkscape

In both of these cases, one source file made use of 'csetjmp'.which display=
s an
error message now.  Changing the include from <csetjmp>' to '<setjmp.h>' wo=
rks
around it.

#    error "If libc++ starts defining <setjmp.h>, the __has_include check
should move to libc++'s <setjmp.h>"

the 2 patches in the respective 'files' directories in the port appear to w=
ork
around it

The real problem seems to be the llvm headers, however, as patching the por=
ts
only works for 14.1 RELEASE (probably)


uname strug:
FreeBSD hack.SFT.local 14.1-RELEASE FreeBSD 14.1-RELEASE GENERIC amd64

NOTE: new xaos patch actually has a second fix in it which I'll submit
separately.  These are both workarounds, really

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281257-227>