[developers] LUI binaries in the main LKB repository

[Alexandre Rademaker]

Hi guys,

Does anyone had a chance to look into it? I can’t reinstall the yzlui … I would be thankful for any help.

Best,
Alexandre


> On 3 Dec 2019, at 10:43, Alexandre Rademaker <arademaker at gmail.com> wrote:
> 
> 
> Hi Stephan and Woodley,
> 
> In http://moin.delph-in.net/LkbLui#Obtaining_and_Running_LUI the link to the MacOS version of LUI (http://sweaglesw.org/linguistics/yzlui-for-osx.tgz) is broken. After updating my MacOS to Catalina, I am getting the error below. I was expecting that reinstalling the library could solve it, any idea?
> 
> 
> ar at leme ace % ./ace -g erg-2018-osx-0.9.30.dat -fl1
> foul and novel terms expressive of rage
> 
> /usr/local/bin/yzlui: line 2: /Applications/yzlui.app/Contents/MacOS/yzlui: Bad CPU type in executable
> /usr/local/bin/yzlui: line 2: /Applications/yzlui.app/Contents/MacOS/yzlui: Undefined error: 0
> LUI: exited
> 
> Best,
> Alexandre
> 
> 
>> On 23 Nov 2019, at 10:23, Stephan Oepen <oe at ifi.uio.no> wrote:
>> 
>> hi again, woodley, i hope i find you well!
>> 
>>> I believe you are right that attempts to make yzlui completely statically linked have been failures ever since the addition of pango support.  I expect to be able to produce a yzlui binary of similar portability to the current LOGON tree’s ACE and FFTB without too much trouble, and will give that a try.
>> 
>> i recently migrated to a new machine and am using the opportunity to
>> try and see whether we can make do without 32-bit compatibility
>> libraries.  so far, i am optimistic (after biting the bullet of
>> re-building the 'swish++' binary for [incr tsdb()], which required
>> tidying up some int-to-pointer casting :-).
>> 
>> this exercise reminded me that the current LOGON tree and the LinGO
>> LKB repository both still only provide 32-bit 'yzlui' binaries.  could
>> you say whether there is a 64-bit binary for linux that you would
>> recommend i use?  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?
>> 
>> best wishes (from rainy oslo)!  oe
>> <yzlui.debug.oe>
>