[MacPorts] #73395: rpki-client @9.7 fails to configure on 32-bit archs

[MacPorts]

#73395: rpki-client @9.7 fails to configure on 32-bit archs
---------------------------+-----------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.11.6
Resolution:                |   Keywords:  ppc, i386
      Port:  rpki-client   |
---------------------------+-----------------------

Comment (by artkiver):

 Thanks for bringing this to my attention!

 At the moment, I don't think I have easy access to any 32bit systems (I
 swapped out a core solo with a core 2 duo in a Mac Mini long ago, which
 stopped functioning sometime after a Mountain Lion OS X Server beta if I
 recall correctly and the other 32bit MacBook I had I think I gave to my
 daughter, who's mom/my ex-wife destroyed it some years ago too. I do have
 some G4 PowerBooks in storage, but I don't make it to my storage unit very
 frequently).

 Regarding the resurrection of https://trac.macports.org/ticket/67883 do
 you think the previous hint of
 https://github.com/att/ast/commit/f85990193bfc14bb88924511ec2d93ad78d536c3
 may be applicable?

 tbh, I don't really make much use of RPKI personally. I am not running BGP
 anywhere (I did in the past, when paid to, but no one is paying me to
 administer their networks and routing infrastructure at the moment) and I
 mostly took over maintainership because I saw that the Portfile had lapsed
 some time behind upstream and I tend to focus a lot on OpenBSD
 development, so figured it wasn't a lot of extra effort to keep
 downstreaming related things, particularly since someone had previously
 created a MacPort.

 In contrast, I have for example, completely avoided creating a MacPort for
 OpenBGPD, not just because I have no infrastructure with which to test it
 currently, or the fact that I never managed to build it from source
 cleanly on macOS; but as someone who has run routing infrastructure at
 for-profit companies, macOS seems ill suited to routing protocols, given
 that without assiduous use of /usr/bin/caffeinate macOS sleeps due to
 power saving design constraints, which are kind of the opposite of 24x7
 paradigms consistent with routing protocols.

 So, the TL;DR is: I am probably not too well equipped to attempt to fix or
 even test such fixes at the moment. ;-/

 That may change in the future! Hopefully. Not too long ago, someone
 suggested I apply for a commit bit, but I told them I was attempting to
 establish a boundary to not take on more responsibilities until I have a
 home again (I am homeless) but given that I was previously sleeping in my
 car, and my car was considered a "total loss" by my insurance company in
 April of last year, and I have not yet acquired a new vehicle? I seem to
 be going kind of the opposite direction of not being homeless, so for the
 time being I am really not taking on more responsibilities so much as
 doing what little I can to help out on occasion, as best I am able, which
 is clearly: insufficient for supporting rpki-client on 32bit OS X systems
 in 2026 at present.

 My sincere apologies.

-- 
Ticket URL: <https://trac.macports.org/ticket/73395#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS