Hello! This is mainly for Barry, but there is no reason that I should send it privately, so...
19:49 <bddebian> WTF generates the .defs.c files? Have a look at the magic in `Makerules.am' and how it is being used in `Makefrag.am'. This is not optimal, but I didn't invent a better way so far. It's also marked as `TODO' in there. 19:56 <bddebian> OK, I get make dist to run, then configure seems to run clean finally on the extracted tarball. But now when running make, I get: 19:56 <bddebian> ld# make 19:56 <bddebian> make all-recursive 19:56 <bddebian> make[1]: Entering directory `/devel2/bdefreese/gnumach-1-11272006/gnumach/build/tmp/gnumach-1.3.99/build' 19:56 <bddebian> make[2]: Entering directory `/devel2/bdefreese/gnumach-1-11272006/gnumach/build/tmp/gnumach-1.3.99/build' 19:56 <bddebian> grep: ../CVS/Root: No such file or directory 19:56 <bddebian> make[2]: *** No rule to make target `vm/memory_object_user.user.defs.c', needed by `../ipc/ipc_entry.c'. Stop. 19:57 <bddebian> make[2]: Leaving directory `/devel2/bdefreese/gnumach-1-11272006/gnumach/build/tmp/gnumach-1.3.99/build' 19:57 <bddebian> make[1]: *** [all-recursive] Error 1 19:57 <bddebian> make[1]: Leaving directory `/devel2/bdefreese/gnumach-1-11272006/gnumach/build/tmp/gnumach-1.3.99/build' 19:57 <bddebian> make: *** [all] Error 2 I checked in a change to oppress the (harmless) error message from grep. No action required from your side. For the actual error message from above, I think I'd need to have a look at the changes you did so far. 22:19 <bddebian> Why is everything nodist_foo.. in Makefrag.am? Those are the files that are generated during the build (e.g. mig's output files) and we thusly don't want to include in a release tarball. Regards, Thomas
signature.asc
Description: Digital signature
_______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
