Andrea Palmatè

On my clib2 everything works correclty with wchar and c++ (except some usual problems with libstdc++.so i have to fix one day). I think i will open it soon because...

> @afxgroup Sounds good. Did you implement the all the wchar_* functions? Yes. With some tests too. However everything needs to test deeply and i'm expecting lot of pull requests...

Repository is now visible https://github.com/afxgroup/clib2

I have the same problem with newlib too.. on address 4. Which compiler are you using?

i had same problem in the past and usually i remove libgcc.so and use the static one. This is the only solution. However dl* function with the actual clib2 doesn't...

mmm.. no. clib2.so will not work. It doesn't exists. But creating .so files and load them with dlopen/dlsym should. The problem is that clib2 is linking crtbegin when creating .so...

Not only. For example the current (ancient) version of GemRB use plugins as .so files and it works without any problem. The problem is not in the .so files but...

i don't know if it is related to newlib (and however i can't fix it since i'm not an os4 dev). However i have a small test case that show...

Wait. I don't want a shared clib2. Clib2 can be static. And for clib2 i mean its libraries. lc lunix and lm. But this doesn't means that i cannot generate...

well, yes. I'm speaking loading objects compiled with clib2. I know that if you try to open an .so compiled with newlib most probably will crash. But it is useful...