[developers] LUI binaries in the main LKB repository

Stephan Oepen oe at ifi.uio.no
Fri Aug 26 13:40:54 CEST 2016

hi again, woodley,

> while synchronizing versions in the LOGON tree vs. the main (or LinGO)
> SVN repository for the LKB, i noticed that the main repository still
> appears to feature separate ‘yzlui’ and ‘pangolui’ binaries, both
> several years older than the unified, pango-enabled ‘yzlui’ binaries
> in the LOGON tree.
> i suspect the LOGON versions have been comparatively widely tested
> since they were last updated (in march 2014, i believe while woodley
> was visiting here), and i am not aware of any known compatibility
> issues.  i suspect the LinGO builds possibly get most used in grammar
> engineering classes at UW (and by other users of your bootable cd
> distribution).

maybe for our first time in the classic class room setting, dan and i
used a version of the LKB with LUI enabled for our grammar engineering
course at ESSLLI last week.  that worked well, though at one point we
maybe felt tempted to temporarily disable the pretty-printing of
lists.  not because of any technical difficulties, but because (a) the
decoration with specialized sub-types (e.g. ‘*optional-null*’
terminating a parameterized list) can look surprising to students at
first and because, more importantly, (b) they sometimes need to think
directly in terms of FIRST and REST sub-structures, e.g. when
implementing a binarized head–complement rule.

either way, i am returning to this older thread about LUI binaries
now, because seeting up for ESSLLI turned up that our current binaries
appear to be 32-bit only:

0 oe at mv (~/src/logon) 82 $ file lingo/lkb/bin/linux.x86.64/yzlui
lingo/lkb/bin/linux.x86.64/yzlui: ELF 32-bit LSB executable, Intel
80386, version 1 (SYSV), dynamically linked (uses shared libs), for
GNU/Linux 2.6.9, stripped
0 oe at mv (~/src/logon) 83 $ svn status lingo/lkb/bin/linux.x86.64/yzlui
0 oe at mv (~/src/logon) 84 $ svn log lingo/lkb/bin/linux.x86.64/yzlui | head
r17155 | sweaglesw | 2014-02-14 20:30:31 +0100 (Fri, 14 Feb 2014) | 1 line

new yzlui binaries
0 oe at mv (~/src/logon) 85 $ cmp lingo/lkb/bin/linux.x86.{32,64}/yzlui
0 oe at mv (~/src/logon) 86 $

—i wonder whether you might recall (or can reconstruct) how we arrived
in this situation?  is there a principled obstacle to creating a
genuine 64-bit binary (i thought not)?

for inclusion in the LOGON tree, however, i am still assuming support
for (older) RHEL6 distributions (where we used to look at ‘patas’ as a
representative build host, but it appears that machine has been
upgraded to a newer installation in the meantime).  if you were to
build a 64-bit binary, would you happen to have access to a suitably
out-of-date build environment still?

with thanks in advance, oe

More information about the developers mailing list