Bug 279370 - [patch] devel/zapcc: marked broken on 15.0
Summary: [patch] devel/zapcc: marked broken on 15.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Dirk Meyer
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2024-05-28 19:31 UTC by Martin Filla
Modified: 2024-06-13 13:08 UTC (History)
2 users (show)

See Also:

Attachments
zapcc-broken15.diff (439 bytes, patch)
2024-05-28 19:31 UTC, Martin Filla 		no flags Details | Diff
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 Martin Filla 2024-05-28 19:31:15 UTC 
Created attachment 251043 [details]
zapcc-broken15.diff

Hi,
this is marked on FreeBSD 15.0

ld.lld: error: version script assignment of 'LLVM_5.0' to symbol 'LLVMCreateDisasm' failed: symbol not defined
ld.lld: error: version script assignment of 'LLVM_5.0' to symbol 'LLVMCreateDisasmCPU' failed: symbol not defined
ld.lld: error: version script assignment of 'LLVM_5.0' to symbol 'LLVMDisasmDispose' failed: symbol not defined
ld.lld: error: version script assignment of 'LLVM_5.0' to symbol 'LLVMDisasmInstruction' failed: symbol not defined
ld.lld: error: version script assignment of 'LLVM_5.0' to symbol 'LLVMSetDisasmOptions' failed: symbol not defined
Comment 1 commit-hook freebsd_committer freebsd_triage 2024-06-13 11:39:42 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=9237ae5a2246263ec05313e8cf699c6127bcf68f

commit 9237ae5a2246263ec05313e8cf699c6127bcf68f
Author:     Dirk Meyer <dinoex@FreeBSD.org>
AuthorDate: 2024-06-13 11:39:19 +0000
Commit:     Dirk Meyer <dinoex@FreeBSD.org>
CommitDate: 2024-06-13 11:39:19 +0000

    devel/zapcc: marked broken on 15.0

    PR: 279370

 devel/zapcc/Makefile | 1 +
 1 file changed, 1 insertion(+)
Comment 2 Jan Beich freebsd_committer freebsd_triage 2024-06-13 12:02:36 UTC 
Did you try LDFLAGS+=-Wl,--undefined-version ? It's often used by other ports to fix similar error. My CPU is kinda busy with other stuff, so I can't test locally.
Comment 3 Martin Filla 2024-06-13 13:08:21 UTC 
(In reply to Jan Beich from comment #2)
No but I can try test