[Bug 293587] www/deno: errors [E0609] on type `Netscape_spki_st` in md4-0.10.2

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 28 Mar 2026 01:29:02 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293587

Chad Jacob Milios <milios@ccsys.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |milios@ccsys.com

--- Comment #4 from Chad Jacob Milios <milios@ccsys.com> ---
(In reply to Mikael Urankar from comment #2)

i too am facing this exact issue, going back weeks or months, in both messy
(host) environments and clean (fresh jail, explicit level-0:build,run &
level-1+:run dependencies only) environments. my ports tree is about 36 hours
old with all pkgs in line with it. i'm on 14.4-RELEASE

however, the problematic environments are far from stock. i built rust using
PORT_LLVM and llvm22, and have ssl=openssl36 llvm=22 among other fairly
aggressive DEFAULT_VERSIONS

im not entirely certain if this is a true bug or just llvm22 becoming more
formal/strict while the pulled-in version of aws-lc-sys is attempting cowboy
antics but i suspect its the latter

i also had an issue that smells quite similar (bindgen going opaque, ie: `pub
_address: u8`) with security/sequoia-sq and its (indirect?) use of the
nettle-sys crate. i just backed it off of llvm22, pegging it to llvm21,
allowing success with the rust-1.94.0 built using PORT_LLVM @ v22

*Key: also, this issue in www/deno went away when using llvm21 across the
board. but i'm still looking to get it working with llvm22 selected. from what
i (barely) understand, this usage of aws-lc-sys here for spkac is vestigial as
stubbed out by spki.rs and could trivially just be stubbed even harder or
cauterized with a minor patch

i would love to see a deno 2.7.x port update (prayers) before we bang our heads
against the wall on this one. might a hero arrive? (checks log) looks like
that's pretty solidly been you, going back a while, Mikael (tyvm, btw). how
challenging and/or tedious was the 2.4.5 -> 2.6.6 work? i'm only an
armchair/barstool scientist. i got $50 toward a deno 2.7.9 update and $50 to
close this bug resolved, combined if killed with one stone, but i myself prolly
wont get on this soon or ever

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