Re: core subdirectories

I don't think that allowing configure to remove a directory with source
under any circumstances is a good idea.  Especially as the people most
likely to interrupt configure are developers who are also most likely to
have modified files that they don't want to loose.

Besides moving a directory in CVS is just a matter of moving the
directory in the repository, then updateding the makefiles.

On Sat, Aug 10, 2002 at 06:16:16PM -0400, Chris Hanson wrote:
>    Date: Sat, 10 Aug 2002 13:58:31 -0700
>    From: Matt Small <[email protected]>
> 
>    Editing the configure script works, but rerunning autoconf will
>    destroy those changes.  I looked around, but I couldn't see a way
>    to put something in the configure.in to tell autoconf not to delete
>    core while it runs.
> 
> This looks like a real problem, but only if the configure script is
> interrupted.  The problem lines are of the form
> 
> trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15
> 
> and they appear throughout the script.  These lines appear to be
> generated automatically by autoconf.
> 
> It hasn't been my experience that running configure causes the core
> directory to be deleted.  (That would be really awful!)  But from
> looking at the code, just typing C-c at the wrong time during its
> execution would cause core to be deleted.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users

-- 
Devin Kowatch
[email protected]


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31