Allan McRae writes:

On 12/04/17 19:33, Magnus Therning wrote:

...

I'm just curious what the reason is.

Because absolutely everything should link to the wide character version.

Wouldn't a symbolic link have the same result? /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Some people, when confronted with a problem, think, “I know, I’ll use LISP.” Now their problem is recursive.

Allan McRae writes:

On 12/04/17 20:09, Magnus Therning wrote:

...

Allan McRae writes:

...

On 12/04/17 19:33, Magnus Therning wrote:

...

I'm just curious what the reason is.

Because absolutely everything should link to the wide character version.

Wouldn't a symbolic link have the same result?

Then you get some software thinking its linked to libncurses.so and some thinking its linked to libncursesw.so. Because they are the same thing, conflict occur and shit hits the fan.

I don't see how. In *both* cases `ldd` will show that the executable is linked against libncurses.so, and in both cases the runtime linker will actually load libncursesw.so (in the case of a link, it follows it; in case of a linker script, it interprets it). To me it seems the outcome is identical: libncursesw.so.6.0 is loaded into the process. /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Some people, when confronted with a problem, think, “I know, I’ll use Haskell.” Now their problem is entirely academic.