Sebastian Bauer

You can submit patches, but of course, they should not break other stuff.

Indeed, it is very unlikely that clib2.so work. I don't remember a change that addressed that and I also never tested it. It also makes sense to use the thread-safe...

Am 2021-01-30 19:02, schrieb Papersoft.it: > mmm.. no. clib2.so will not work. It doesn't exists. I meant .so generated with the clib2 flavor. I think I have disabled the generation...

Am 2021-01-31 11:49, schrieb Papersoft.it: > Not only. For example the current (ancient) version of GemRB use > plugins as .so files and it works without any problem. The problem...

Am 2021-01-31 16:38, schrieb Papersoft.it: > Wait. I don't want a shared clib2. Clib2 can be static. And for clib2 > i mean its libraries. lc lunix and lm. >...

Am 2021-02-02 11:48, schrieb kas1e: > @sba1 [1] > There is some mess started: We have now 3 different versions of clib2. > One in adtools, another one is a...

>> Use the original one in gcc but keep in mind that something doesn't >> work if you don't change it deeply > And as seems, clib2 wasn't targeting at...

How about moving this discussion to somewhere else? Github discussions at our adtools group comes into my mind. This would be visible then to @adtools/developers as well. I would be...

Am 2021-02-07 09:37, schrieb kas1e: > Giving the VERY unacceptable and slow pool request reviews and > accepting or rejecting them, you of course kill all sodero's > motivation to...

Generally, it would help a lot if for all known problems, a simple test source code is provided that can be added in the test folder, even if the problem...