autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Platform-specific "clean" targets?


From: Jay Levitt
Subject: Re: Platform-specific "clean" targets?
Date: Sat, 17 Nov 2007 14:21:19 -0500
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)

On 11/17/2007 2:12 PM, Noah Misch wrote:
On Sat, Nov 17, 2007 at 01:51:43PM -0500, Jay Levitt wrote:
On Stratus VOS, core files are not called "core"; they are called "[executable_name].kp". Is there something I can do in config.site (or somewhere else) that will propagate through autoconf to add this to the average autoconf/automake project's "clean" target - ideally at "configure" time, not autoconf or automake time? The clean-local target seems to be for project-specific targets, not platform-specific targets, and I'm not sure how to affect it from config.site anyway.

`make clean' should not delete such core files, since `make' does not create
them.  It is appropriate for `configure' to delete `conftest.kp' that may remain
after a failed test, and it can do this unconditionally.

Yeah, that makes sense. I thought I'd seen other cases where make clean did an "rm core", but I've mostly been building "metaprojects" like gnulib and autoconf, where a core might be expected during failed tests. The usual "rm conftest*" in configure should catch any conftest keep files too.

There is no general facility designed to augment the clean rule on a platform-
or site-specific basis.

OK, didn't think so - just wanted to check.  Thanks.

Jay




reply via email to

[Prev in Thread] Current Thread [Next in Thread]