tde-devs@chat.jabb.im < 2022/10/10 >
[06:22]michelec2 has joined
[06:22]michelec2 has left
[18:15]hunter0one has joined
[18:16]hunter0one: Hello
[18:17]Slávek: hello
[18:17]Slávek: nice to meet you
[18:17]hunter0one: Hi Slavek, I've been here before. I wasn't sure if this was dead because of the spam I saw :-)
[18:18]hunter0one: I just finished building TDE on FreeBSD last night, there were a few notes I took
[18:18]Slávek: Unfortunately, spam has been saved in the history of the Jabber server and until there is a sufficient number of new messages, it will be loaded as "recent" messages.
[18:19]hunter0one: (Y)
[18:20]Slávek: Great, I didn't make a new building on FreeBSD for a long time, so it will be good to know the current information to release R14.0.13 was fine.
[18:21]hunter0one: It's gone smoothly but there were two hiccups, I'm thinking of making a live USB of FreeBSD that comes with TDE after R14.0.13.
[18:23]hunter0one: I should've ran a typescript when I was building but I hadn't. "libksqurrel" got removed by pkg because I recall something down the line in the "applications" category wanted librsvg2-rust instead of librsvg2
[18:24]hunter0one: Looks like it was gtk3-tqt-engine-trinity because if I try to remove librsvg2-rust it removes this specifically
[18:24]hunter0one: I have ksquirrel installed but without the library it won't run of course
[18:33]hunter0one: I'm about to see if libksquirrel will work with librsvg2-rust instead
[18:44]hunter0one: It did build and install fine but if I recall in my last complete build 4-5 months ago ksquirrel + libksquirrel built fine but ksquirrel crashed. Its doing the same now but I don't have debug symbols to really tell anything from it.
[18:47]Slávek: you can set TDE_DEBUG to 1 in trinity.port.mk
[18:50]hunter0one: (Y)
[18:54]hunter0one: Also I had to add pcre as a dependency for tdelibs, otherwise I got a "pcre support are requested but not foudn on your system" error
[18:54]hunter0one: devel/pcre
[19:25]hunter0one: Hmm, I turned on TDE_DEBUG and built libksquirrel and ksquirrel both but it still gives me the same output: "This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash"
[19:27]Slávek: Do you start the ksquirrel and then connect with dbg or you start dbg and the ksquirrel within it?
[19:27]Slávek: If I remember well, I had to use the second way.
[19:29]hunter0one: I was trying to read the backtrace from the TDE Crash Handler, but I've also tried "gdb ksquirrel" but for some reason this causes gdb to become a runaway process after I try to run ksquirrel
[19:30]hunter0one: Reading symbols from ksquirrel...(gdb) runStarting program: /opt/trinity/bin/ksquirrelptrace (PT_LWPINFO): Operation not permitted.
[19:34]hunter0one: Oh yeah, tdesdk also fails to build because ninja reports that a subcommand failed
[19:35]hunter0one: tdesdk and ksquirrel are really the only two trouble ports I've found
[19:43]hunter0one: I'll be back, I need to restart X
[19:43]hunter0one has left
[19:48]hunter0one has joined
[20:06]hunter0one has left
[20:14]hunter0one has joined
[21:35]hunter0one has left

tde-devs@chat.jabb.im < 2022/10/10 >