Re: 21.5b9 on MacOSX build problem

Adrian Aichner wrote: I do. Over 60MB of them. They are just not visible to this xemacs in its build directory. They are in /sw/lib/xemacs/ and they will be visible when xemacs is installed. I am not quite the newbie this problem makes me seem to be. I have compiled xemacs on various systems from the times when it was called lemacs, and I am using it daily in my work. I did spend quite some time trying to debug this myself before writing to the list, but I admit that it is over my head. There was also some discussion on the fink mailing lists about this problem, but no idea emerged, partly because no real xemacs experts were present, but mainly because this is something that only happens to some people and not to others, although they all use exactly the same build system with the same configure and compile options. It does. I have tried all command line option variants I can imagine. This error must be somewhere in the preloaded lisp packages or rather in their dumped form. But I am sure this error is only a symptom of something else, maybe a buffer overflow in the dump process or something. In fact, here is a suspicion: Is it possible that the list of filenames in the dumped xemacs can get too long? I find there more than 10000 bytes of filenames of the form /Volumes/Software/sw/src/xemacs-21.5.9-1/xemacs-21.5.9/lisp/post-gc.elc /Volumes/Software/sw/src/xemacs-21.5.9-1/xemacs-21.5.9/lisp/replace.elc /Volumes/Software/sw/src/xemacs-21.5.9-1/xemacs-21.5.9/lisp/cmdloop.elc and so on. As I have tried to explain before, if I compile with slightly different options, I get a crash at the same place, but with different error messages. Depending on the options, this can be a lisp error or a C error (bus error). When I omit the option '--error-checking=none', then the compilation terminates successfully. When I run "make" by hand from the command line, I get a different result from when I run the same make from inside the fink build script. I also compared build output logs from a successful build and an unsuccessful one. Apart from some lines that acknowledge the activated error checking, the two outputs are strictly identical up to the fatal error around line 1655 or so. -- Martin