[developers] LUI binaries in the main LKB repository

[Woodley Packard]

Hi Stephan et al.,

It appears that the fontconfig folks decided to do a major change in the 
format of their configuration file, breaking compatibility with the 
statically linked fontconfig library built into the yzlui binaries built 
on my computer.  This hilights a basic problem with the idea of 
statically linking binaries and expecting them to run on everybody's 
computer.  If you want a statically linked fontconfig library, you 
basically have to bundle the fontconfig configuration files too, and for 
all I know all of the fonts as well.

It appears the yzlui that is in the LOGON tree is actually dynamically 
linked with respect to fontconfig.  I built such a 64-bit Linux yzlui 
and uploaded it for you and anyone else who is interested to try out.  
Hopefully this is the right balance between static and dynamic?

http://sweaglesw.org/linguistics/yzlui.64.dynamic-fontconfig

It is built on a machine with a 4.2 kernel, but according to `file', the 
ABI is Linux 2.6.32.  I will be curious to hear success or failure stories.
-Woodley

On 11/23/2019 05:23 AM, Stephan Oepen wrote:
> i turned to the internet and picked up a binary that
> appears to be built for compatibility with older kernels and seems to
> kind of work for me:
>
> http://sweaglesw.org/linguistics/yzlui-NET_WM_NAME
>
> by default, however, i end up with monospaced fonts only: a cursory
> look at '/tmp/yzlui.debug.oe' (attached) suggests that we may be
> running into hard limits on compatibility; i am guessing the above
> 'yzlui' binary has an older version of fontconfig compiled in, but my
> brand-new local font repository no longer can be accessed using that
> code.
>
> the above 64-bit binary appears more statically compiled than the
> 32-bit binary that i suspect most people have been using for the past
> several years:
>
> $ md5sum $LOGONROOT/lingo/lkb/bin/linux.x86.{32,64}/yzlui
> 47dd0773914e7af244e9a903fa70e9c9
> /home/oe/src/logon/lingo/lkb/bin/linux.x86.32/yzlui
> 47dd0773914e7af244e9a903fa70e9c9
> /home/oe/src/logon/lingo/lkb/bin/linux.x86.64/yzlui
> $ ldd $LOGONROOT/lingo/lkb/bin/linux.x86.32/yzlui
>          linux-gate.so.1 =>  (0x00b2d000)
>          libm.so.6 => /lib/libm.so.6 (0x00cc9000)
>          libpthread.so.0 => /lib/libpthread.so.0 (0x00c52000)
>          libXext.so.6 => /usr/lib/libXext.so.6 (0x0092b000)
>          libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x003fc000)
>          libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00d02000)
>          libc.so.6 => /lib/libc.so.6 (0x001a3000)
>          libX11.so.6 => /usr/lib/libX11.so.6 (0x00431000)
>          libdl.so.2 => /lib/libdl.so.2 (0x00c4b000)
>          /lib/ld-linux.so.2 (0x00a8f000)
>          libexpat.so.1 => /lib/libexpat.so.1 (0x00dad000)
>          libxcb.so.1 => /usr/lib/libxcb.so.1 (0x0033a000)
>          libXau.so.6 => /usr/lib/libXau.so.6 (0x00da8000)
>
> would you be in a position to compile a 64-bit binary, preferably
> still in a 2.6-kernel environment, with a similar set of external
> dependencies?