Op maandag 02-11-2009 om 13:29 uur [tijdzone -0800], schreef Patrick McCarty:
> I've tried doing `sh -x ./fixinc.sh', but that didn't reveal any > clues. > > I suppose I'll try doing a `sh -x ./fixinc.sh' with > freebsd-x86::cross/gcc, which uses gcc 4.3.2 too (and is succeeding). > Comparing the logs might provide some hints. That's something like what I would do. You can also try doing bash -x and compare the log with sh -x. And beware of LIBRESTRICT errors of course, those can have nasty effects -- esp. in "languages" like sh or perl that just continue upon an error. > Are there any other ways to debug this issue besides shell tracing? Is fixinc.sh being generated? Greetings, Jan. _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
