[arch-general] Why is /lib/libncurses.so a linker script?

[Magnus Therning]

Allan McRae <allan at archlinux.org> writes:

> On 12/04/17 20:09, Magnus Therning wrote:
>>
>> Allan McRae <allan at archlinux.org> 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 at therning.org   jabber: magnus at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20170412/84fdd38c/attachment-0001.asc>