coredumping in malloc for lexer

[Hume Smith]

Maybe someone's seen this.
I just compiled lilypond 1.2.17, with default configuration and a couple of tweaks. I used the precompiled NetBSD packages for everything else, except flex, which I had to compile from 2.5.4. (the source package said flex 2.5.4a didn't work on 1.4.1/i386, and maybe its so...)
I initially had a problem with lexer at the linking stage; _yy_flex_alloc _yy_flex_realloc and _yy_flex_free were undefined. I tried the obvious thing of adding #define yy_flex_alloc malloc etc in lexer.ll... now lilypond runs but eventually coredumps. it looks like an infinite recursion in malloc:
(gdb) bt
#0 0x17c08b in malloc (size=20) at lexer.ll:1168
#1 0x17c090 in malloc (size=20) at lexer.ll:1168
#2 0x17c090 in malloc (size=20) at lexer.ll:1168
#3 0x17c090 in malloc (size=20) at lexer.ll:1168
#4 0x17c090 in malloc (size=20) at lexer.ll:1168
#5 0x17c090 in malloc (size=20) at lexer.ll:1168
#6 0x17c090 in malloc (size=20) at lexer.ll:1168
... for hundreds of frames.
Can anyone tell me the right way to handle the yy_flex_<memory> things?



--