[tex-live] dvisvgm can't find libgs

[Pander]

"Florêncio Neves" <florencioneves at gmail.com> wrote:

>In Debian 6, libgs is at /usr/lib/libgs.so.8 and
>/usr/lib/libgs.so.8.71 and dvisvgm couldn't find.  Debian ships a file
>/usr/lib/libgs.so in the package libgs-dev, but I didn't have it
>installed and I guest most users won't either.

Please note that sine "recently" gcc requires -l options to follow after -o option. Perhaps that is messing things up.

>Thanks,
>F.
>
>On 11/16/12, Martin Gieseking <martin.gieseking at uos.de> wrote:
>> Am 15.11.2012 23:59, schrieb Karl Berry:
>>>     The version of dvisvgm distributed with TeXLive 2012 can't seem
>to
>>>     find libgs automatically
>>>
>>> It works for me on CentOS 5.  I have /usr/lib/libgs.so there.
>>>
>>>     if I point its location with --lib-gs
>>>
>>> This sounds like your libgs.so is somewhere that it doesn't know to
>>> look.
>>>
>>> In any event, thanks for the report, but this is an issue with
>dvisvgm,
>>> not TeX Live, so can you please send the report to the maintainer,
>>> Martin Gieseking <martin.gieseking at uos.de>?  Please also tell him
>where
>>> your libgs.so is, since presumably that's the critical piece of
>>> information.
>>
>> I think Florêncio refers to the linkage variant used to build the
>> dvisvgm binary. Ghostscript can be linked directly so that the
>> PostScript support is always available. In this case, the dvisvgm
>> command-line option --libgs is not present. The executable just
>requires
>> the properly versioned libgs, e.g. libgs.so.9.
>>
>> If the libgs development files were not installed during the build
>> process, the resulting binary tries to load libgs.so via dlopen(),
>and
>> additionally provides option --libgs that can be used to give an
>> alternative filename.
>>
>> At least, this is the default behavior of the original dvisvgm build
>> system. I'm not sure if the modified configuration files in TeX Live
>> offer the same build variants too.
>>
>> Regards,
>> Martin
>>