Tiny Core Extensions > TCE Bugs

hexchat error while loading shared libraries: libssl.so.1.0.0 in CorePure64 11.1

<< < (2/3) > >>

licoti:
Again, thanks,

does that information (and links) still reflect the current requirements for 64 bit?
Can I also find current recommended build-script templates from there? (while on the subject :) )

(I've been dabbling in TC on and off the last years, prior to making it my daily driver since january this year).

Live addition, thanks for pointing me to the correct thread regarding badwolf!

Thanks again Rich!

Rich:
Hi licoti

--- Quote from: licoti on November 28, 2020, 10:38:04 AM --- ... does that information (and links) still reflect the current requirements for 64 bit? ...
--- End quote ---
The Wiki should be current.


--- Quote --- ... Can I also find current recommended build-script templates from there? (while on the subject  ) ...
--- End quote ---
Recommended? No. But you can find a couple of samples of what I've done here:
http://forum.tinycorelinux.net/index.php/topic,2588.msg154649.html#msg154649

licoti:
Thanks a bunch,

then I will discard some stuff I learned past year on 10.1 32 bit, and start fresh from this jumping point!

Juanito:
If you'd like to submit an update to hexchat, please go ahead.

licoti:

Thanks for responding Juanito!

current hexchat in 11.x 64bit repo is version 2.10.2

Hexchat changelog (https://hexchat.readthedocs.io/en/latest/changelog.html) mentions:

2.12.4 (2016-12-10)
- fix building against OpenSSL 1.1

2.14.0 (2018-03-10)
- rewrite build system in Meson
- fix building against OpenSSL 1.1.0

2.14.3 (2019-12-20)
- fix various incorrect parsing of IRC messages relating to trailing parameters

Note, the above are only the most important highlights.

It appears to me this means we'd need to upgrade to at least 2.14.0, but preferably 2.14.3 (which then is also the latest release) because fixing it's input stream parser to correctly handle trailing paramaters in the irc messagestream isn't the only very important fix.

It doesn't feel right to me to unilaterally decide for the community what compile-time options are to be selected (script-support, which supported script-languages, theme support, etc.).

I also haven't yet encountered this 'mason' thing and have some stuff open in my current session, I'd need at least a day before I can do a clean base-line reboot.

Perhaps, the best thing to do is for me to post the available compile-time options asap, which options were currently selected in 2.10.2 (from the src link Rich provided), and what seems to be equivalent (couse if it was just for me I'd disable script support and 'send system stats' etc..).

What's the usual workflow here (when deciding compiled options in preparing an extension for the community)?

Navigation

[0] Message Index

[#] Next page

[*] Previous page