Wednesday, May 27, 2026

Re: Fastnetmon OpenBSD Port update,

Folks 
Im building Stuarts updated port  for fastnetmon taking account of the 27 CVES fixed in latest release, 

just wondeiring about errors such as
 warning: unknown warning option '-Wmaybe-uninitialized'; did you mean '-Wuninitialized'? [-Wunknown-warning-option]
warning: unknown warning option '-Wcatch-value=3' [-Wunknown-warning-option]
warning: unknown warning option '-Wclass-memaccess'; did you mean '-Wclass-varargs'? [-Wunknown-warning-option]

to reduce these unrecognized  options warnings  should I suggest an OpenBSD specific Make file  with the correct options for OpenBSD for upstream.. .
?
what is the best way to approach this to reduce porters workload ? 

Thanks 
Tom Smyth



On Sat, 23 May 2026 at 13:48, Stuart Henderson <stu@spacehopper.org> wrote:
use 'make FETCH_PACKAGES=' to use packages for deps so you don't need to build cmake etc

-- 
  Sent from a phone, apologies for poor formatting.


On 23 May 2026 12:47:47 Tom Smyth <tom.smyth@wirelessconnect.eu> wrote:

Hi folks, 

I updated src and ports on Thursday evening,  
and then copied and extracted fastnetmon.tgz t /usr/ports/net/fastnetmon

make clean
make fix-permissions 
make 
worked ok 

make install threw a few errors
4 errors generated.
*** Error 1 in target 'Source/CMakeFiles/CTestLib.dir/CTest/cmCTestCurl.cxx.o'
*** Error 1 in . (Source/CMakeFiles/CTestLib.dir/build.make:222 'Source/CMakeFiles/CTestLib.dir/CTest/cmCTestCurl.cxx.o')
*** Error 2 in . (CMakeFiles/Makefile2:2029 'Source/CMakeFiles/CTestLib.dir/all')
*** Error 2 in /usr/ports/pobj/cmake-core-3.31.8/cmake-3.31.8 (Makefile:169 'all')
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:3069 '/usr/ports/pobj/cmake-core-3.31.8/.build_done': @...)
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:2241 '/usr/ports/packages/amd64/all/cmake-core-3.31.8.tgz')
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:2239 '/usr/ports/packages/amd64/all/cmake-core-3.31.8.tgz')
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:2730 'subpackage': @:; (case X${_DEPENDS_CACHE} in  X) ...)
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:2259 '/var/db/pkg/cmake-core-3.31.8/+CONTENTS': @cd /us...)
*** Error 2 in /usr/ports/devel/cmake/core (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'install': @lock=cmake-core-3.31.8;  export _LOCKS...)
*** Error 1 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2392 '/usr/ports/pobj/capnproto-1.2.0/.dep-devel-cmake-core')
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2804 '/usr/ports/pobj/capnproto-1.2.0/.extract_done': @c...)
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2241 '/usr/ports/packages/amd64/all/capnproto-1.2.0.tgz')
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2239 '/usr/ports/packages/amd64/all/capnproto-1.2.0.tgz')
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2730 'subpackage': @:; (case X${_DEPENDS_CACHE} in  X) _...)
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2259 '/var/db/pkg/capnproto-1.2.0/+CONTENTS': @cd /usr/p...)
*** Error 2 in /usr/ports/devel/capnproto (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'install': @lock=capnproto-1.2.0;  export _LOCKS_HE...)
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2392 '/usr/ports/pobj/fastnetmon-1.2.9pre20260425/.dep-devel-capnproto': @unset _...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2804 '/usr/ports/pobj/fastnetmon-1.2.9pre20260425/.extract_done': @cd /usr/ports/...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2241 '/usr/ports/packages/amd64/all/fastnetmon-1.2.9pre20260425.tgz': @cd /usr/po...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2239 '/usr/ports/packages/amd64/all/fastnetmon-1.2.9pre20260425.tgz': @cd /usr/po...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2730 'subpackage': @:; (case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$(/usr/bin/...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2259 '/var/db/pkg/fastnetmon-1.2.9pre20260425/+CONTENTS': @cd /usr/ports/net/fast...)
*** Error 2 in /usr/ports/net/fastnetmon (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'install': @lock=fastnetmon-1.2.9pre20260425;  expor...)


Ill re-sync the  ports and src and try again, 


On Thu, 21 May 2026 at 16:46, Tom Smyth <tom.smyth@wirelessconnect.eu> wrote:
Hi Stuart Ill test on 7.9 release, Ill test on current failing that 

Thanks 



On Thu, 21 May 2026 at 16:36, Tom Smyth <tom.smyth@wirelessconnect.eu> wrote:
Hi Stuart, 

Ill Give this a test now, 

Thanks 

Tom Smyth 

On Thu, 21 May 2026 at 16:17, Stuart Henderson <stu@spacehopper.org> wrote:
On 2026/05/21 10:47, Tom Smyth wrote:
> Folks, 
> I was talking to Pavel  (from fastnetmon) and  he responded posively asked the following 
>
> "Can you provide summary what's required from our side? " 

probably nothing

you could give this a spin?



--
Kindest regards,
Tom Smyth.


--
Kindest regards,
Tom Smyth.


--
Kindest regards,
Tom Smyth.



--
Kindest regards,
Tom Smyth.

Re: UPDATE: wayland/wlroots-0.19 --> 0.19 & 0.20

Hi Robert, On 5/27/26 9:00 PM, Robert Lillack wrote: > Hi Volker, > > thanks for the feedback! > > Am Di, 26. Mai 2026, um 20:44, schrieb Volker Schlecht: > >> * My instinct would be to name the SUBDIRs 19 and 20 instead of 0.19 and 0.20 > > Looking at existing multi-version ports in the tree, the dotted > convention seems to be consistent: lang/lua/{5.1,5.2,5.3,5.4}, > lang/python/{2.7,3}, lang/ruby/{3.3,3.4,4.0}. I couldn't find a > precedent for stripping the dot, so I went with what's already > established. I didn't claim to have particularly good instincts... >> * I think that you need to add a "@pkgpath wayland/wlroots" to the PLISTs > > Added this to 0.19/pkg/PLIST. Following lang/lua/5.1/pkg/PLIST, only the > version that previously lived at the un-versioned path declares the old > pkgpath. Right? If by the time 8.0 is released, all wlroots consumers are using wlroots-0.20 I think it will be needed in 0.20 too, to provide an upgrade path from wlroots in 7.9-stable to 8.0-stable. It's very possible that I'm wrong, though. cheers, Volker