Re: RE : rm -f core cause some troubles

[Paul Eggert]

On 12/08/2012 10:12 AM, PICCA Frédéric-Emmanuel wrote:
>> That would slow down 'configure' everywhere.
> 
> how much ?

I don't know.  I expect it'd be measurable, though.

> if you add an option each time a directory name or other file is not 
> allowed...

Yes, perhaps it's not a good idea.

> I renamed core -> Core, and this issue just gone.

I don't know why that would be, but perhaps more digging
on your end can find out.

Here's another idea.  Define your own 'rm',
which will be a simple shell script that invokes the
real 'rm', except it ignores any 'core' argument.  Put
it in your PATH, before the real 'rm'.  Then run
configure with that PATH.  That should work.

And here's another another idea.  When building
'configure', do it like this:

   autoconf
   sed 's/ core / /g' configure >config.cache
   cp config.cache configure

That way, your 'configure' won't try to remove 'core'.
It's a bit of a hack, but it should work.