Date: Fri, 14 Sep 2018 15:29:09 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 231361] weechat failing to load ruby.so after recent updates Message-ID: <bug-231361-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231361 Bug ID: 231361 Summary: weechat failing to load ruby.so after recent updates Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: twasson@gmail.com I recently restarted weechat for the first time in awhile (1-2 months), and= now it can't load ruby.so because of: Error: unable to load plugin "/usr/local/lib/weechat/plugins/ruby.so" /usr/local/lib/weechat/plugins/ruby.so: Undefined symbol "ruby_version" `strings /usr/local/lib/weechat/plugins/ruby.so` reveals that ruby_version = is in the file. I first saw this with the binary pkg installation, but I've rebuilt weechat from source from the ports tree and that didn't resolve the problem. I also updated to 11.2-RELEASE after I first saw this, which also= had no effect, incidentally. ktrace revealed nothing useful, and I'm not sure = what I should look for with dtrace. `nm -D /usr/local/lib/weechat/plugins/ruby.so`, however, reveals that the symbol is present but undefined. I tried editing linker flags in the cmake script but couldn't figure out how to make clang disable undefined symbols. I mailed freebsd-ports about this and received a confirmation of this issue= on CURRENT with weechat 2.2 and ruby 2.4.4 from Kubilay Kocak. I suspect this is more likely to be a FreeBSD-specific problem than a gener= al weechat problem, as I see no reports (other than a random pastebin paste) of this anywhere online. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231361-7788>