Bug 281257 - base llvm csetjmp C++ header file now generates an error
Summary: base llvm csetjmp C++ header file now generates an error
Status: Closed DUPLICATE of bug 279692
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 14.1-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-toolchain (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-09-03 21:52 UTC by Bob Frazier
Modified: 2024-09-05 08:33 UTC (History)
1 user (show)

See Also:

Attachments
shar file for graphics/xaos containing patch (16.35 KB, text/plain)
2024-09-03 21:52 UTC, Bob Frazier 		no flags Details
shar file for graphics/inkscape containing a patch (workaround) (250.82 KB, text/plain)
2024-09-03 21:57 UTC, Bob Frazier 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Frazier 2024-09-03 21:52:38 UTC 
Created attachment 253310 [details]
shar file for graphics/xaos containing patch

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

graphics/xaos
graphics/inkscape

In both of these cases, one source file made use of 'csetjmp'.which displays an error message now.  Changing the include from <csetjmp>' to '<setjmp.h>' works 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 work around it

The real problem seems to be the llvm headers, however, as patching the ports 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
Comment 1 Bob Frazier 2024-09-03 21:57:33 UTC 
Created attachment 253311 [details]
shar file for graphics/inkscape containing a patch (workaround)

not intended as a permanent fix (either one actually)
Comment 2 Bob Frazier 2024-09-03 22:47:42 UTC 
we can add devel/glog to the list of affected ports
Comment 3 Dimitry Andric freebsd_committer freebsd_triage 2024-09-05 08:33:21 UTC 
Duplicate of bug 279692.

*** This bug has been marked as a duplicate of bug 279692 ***