Fix 1821: Write pathes for ly-to-tely to a separate file rather than passing as cmd line args

Fix 1821: Write pathes for ly-to-tely to a separate file rather than passing as cmd line args

For out-of-source builds, the collated files list has the whole absolute path
for each and every file (>1000 for our regtests), which blows up the cmd line
length to values that don't work with the shell (<=131000 chars allowed...).

This patch takes the list in the makefile and writes the filenames in several
patches (300 at a time for now) to a .list file and then passes just this one
file to lys-to-tely, which reads in the whole long list of file names from that
file. The trick is that while make can handle long variables, we can't pass
it to ly-to-tely on the cmd line, but have to use a helper file.

[Graham Percival (old account), 2011-08-31 04:26:59]

sweet mao that's disgusting.  I love it.  :)

If you can make doc from scratch, then push.

[reinhold_kainhofer.com, 2011-08-31 12:56:59]

Am Mittwoch, 31. August 2011, 06:26:59 schrieb percival.music.ca@gmail.com:
> sweet mao that's disgusting.  I love it.  :)
> 
> If you can make doc from scratch, then push.

Actually, with my test setup, I can't even build lilypond, because metafont 
already fails with some long pathes:

I created the path "/data/lilypond/This-is-a-very-long-path-to-the-lilypond-
source-directory/And-it-contains-several-long-sub-directories/Which-should-
break-the-makefile/Because-the-call-to-lys-to-telys-will-be-longer-than-the-
allowed-130000-characters/" and symlinked my lilypond sourcedir there. Then I 
configured an out-of-source build in /data/lilypond/build1 and ran make. The 
binary built fine, but metapost fails with a memory corruption in glibc! In 
particular:


lilypond@curie:~/build1/mf/out$ mpost -progname=mpost -ini 
/data/lilypond/This-is-a-very-long-path-to-the-lilypond-source-directory/And-
it-contains-several-long-sub-directories/Which-should-break-the-
makefile/Because-the-call-to-lys-to-telys-will-be-longer-than-the-
allowed-130000-characters/lilypond/mf/mf2pt1.mp \\dump

This is MetaPost, version 1.208 (kpathsea version 5.0.0) (INIMP)

(/data/lilypond/This-is-a-very-long-path-to-the-lilypond-source-directory/And-
i
t-contains-several-long-sub-directories/Which-should-break-the-
makefile/Because
-the-call-to-lys-to-telys-will-be-longer-than-the-allowed-130000-
characters/lil
ypond/mf/mf2pt1.mp*** glibc detected *** mpost: double free or corruption 
(!prev): 0x0a0ebab0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x6b961)[0x17b961]
/lib/i386-linux-gnu/libc.so.6(+0x6d28b)[0x17d28b]
/lib/i386-linux-gnu/libc.so.6(cfree+0x6d)[0x18041d]
mpost[0x80625f1]
mpost[0x8062686]
mpost[0x8077f90]
mpost[0x808c08b]
mpost[0x804ad3d]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x126e37]
mpost[0x80495f1]
======= Memory map: ========
00110000-0026a000 r-xp 00000000 08:01 1097937    /lib/i386-linux-
gnu/libc-2.13.so
0026a000-0026b000 ---p 0015a000 08:01 1097937    /lib/i386-linux-
gnu/libc-2.13.so
0026b000-0026d000 r--p 0015a000 08:01 1097937    /lib/i386-linux-
gnu/libc-2.13.so
[...]

Any idea?

Cheers,
Reinhold

-- 
------------------------------------------------------------------
Reinhold Kainhofer, reinhold@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

[wl_gnu.org, 2011-08-31 17:55:56]

> Actually, with my test setup, I can't even build lilypond, because
> metafont already fails with some long pathes: [...]
> 
> Any idea?

Please report this to the texlive@tug.org


    Werner