I have two problems with running config.status: it's flaky when you change CONFIG_FILES and CONFIG_HEADERS (for instance, instead of deleting the output file on a signal, it deletes all my makefiles) it can't be run concurrently (as in a make -j2). I know how to fix these problems, by modifying the config.status file slightly. Where in autoconf would I look to do this consistently? -- Benoît
- Re: [autoconf] hacking with config.status Benoit Hudson
- Re: [autoconf] hacking with config.status Alexandre Oliva