On 17.11.2020 09:00, Martin Husemann wrote:
On Mon, Nov 16, 2020 at 07:54:38PM +0100, Bodie wrote:[19:45:55:337] [2861:67ec4000] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [19:45:55:358] [2861:67ec4000] [INFO][com.freerdp.core] -freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting errorstateWhy do you think this is related to the timer_* issue that they fixed?
Because I am still getting this: $ uname -aNetBSD hostname 9.1_STABLE NetBSD 9.1_STABLE (GENERIC) #0: Sat Nov 14 15:38:43 UTC 2020 mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
$[09:28:48:378] [2337:82f08000] [ERROR][com.winpr.synch.timer] - InitializeWaitableTimer: os specific implementation is missing
In my build log I see: -- Looking for timer_create - found -- Looking for timer_delete - found -- Looking for timer_settime - found -- Looking for timer_gettime - found so this looks good.
Should I see these syscalls in ktruss output? Because I can't see them
The client command line and help is so obfuscated thought that I did notmanage to actually use it: [08:55:19:195] [17803:40b2bc00] [ERROR][com.freerdp.core] - nla_recv_pdu:freerdp_set_last_error_ex ERRCONNECT_LOGON_FAILURE [0x00020014]... which probably means I got some \ wrong or used bogus authenticationoptions.
In FreeBSD they did this https://github.com/FreeRDP/FreeRDP/pull/4608/files as patch file to that winpr/libwinpr/CMakeLists.txt , but in pkgsrc I can't see it in patches (and to be honest not sure if it is needed if NetBSD has
timer_create and others)
Martin