This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Update backward/algo.h


On Mon, Dec 31, 2001 at 08:29:03AM -0800, Benjamin Kosnik wrote:
> 
> > When did it become a non-issue?  And, how?  
> 
> The Makefiles already install non-.h headers. See 'include/std/*' and 
> include/Makefile.am. The make install rules for headers are not the make 
> defaults (for other reasons, actually.)

The problem was never installing non-.h headers.  The problem was 
depending on non-.h headers.  In particular, if you have a foo.cc 
and a header foo that it depends on, make is very likely to delete 
your header foo if you SIGINT the make while it is building foo.o.

Benjamin:

1. Are you certain you understood the problem in the first place?
2. Was there a specific version of gmake where this behavior was fixed?  
3. Are we sure we're using a fixed version of gmake when building, or
   a non-gmake that doesn't have a matching bug?

I don't like seeing a carefully designed structure allowed to rot
just because nobody can be bothered to understand why it was built,
and then tearing it down because it was allowed to rot.

Gaby:

Do you have any reason to believe that src_dir != build_dir
protects against gmake deleting files in src_dir?
 
> > Note there are many extra files that exist solely to conform 
> > to the rule.  Absent the rule they should be deleted.
> 
> Can you spec this out this work please?

I will if I have some assurance that I'm not wrecking something
that a lot of work went into building.  

Nathan Myers
ncm at cantrip dot org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]