Thanks a lot! I'm afraid the new C file issue is interacting with some other problem in a strange way. I find that running this:
../meta/uninstalled-env guile-tools in the command line in libguile will produce the message "Abort trap". That command is run as part of the larger command cat <lots of .doc files> | GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools snarf-check-and-output-texi > guile-procedures.texi as part of the build process, which is what was causing my build to fail. However, if I run it with a regular guile interpreter instead of the uninstalled-env one, it works fine: cat <lots of .doc files> | GUILE_AUTO_COMPILE=0 ../../bin/guile ../meta/guile-tools snarf-check-and-output-texi > /dev/null returns normally. Therefore I believe there is a bug in meta/uninstalled-env, but I'm unsure why building the git trunk seemed to work fine. Could you (or anyone) guess what this might be? Thanks Noah On Tue, Jun 15, 2010 at 4:34 PM, Andy Wingo <wi...@pobox.com> wrote: > On Tue 15 Jun 2010 16:06, Noah Lavine <noah.b.lav...@gmail.com> writes: > >> I've tried this, but I still get the error. Currently my files are in >> every long list of files (.c, .doc, .x, and .h), and I don't see any >> other places where source files for the main Guile program are listed. >> Is there anything else I can try? > > Perhaps I misstated: > >>> If you don't use SCM_DEFINE et al, you >>> might not need to copy the .doc or .x lines. > > That should be, "you might need not to copy ..." :) Try removing the > .doc and/or .x forms. > > Andy > -- > http://wingolog.org/ >
