This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Overriding DW_AT_comp_dir output?


On Dec  7, 2003, neroden@twcny.rr.com (Nathanael Nerode) wrote:

> The need to build each stage in exactly the same directory layout is evil

Why?  I find it quite nice to be able to cd to the same directory to
figure out where the build failed.  Using separate directories, I'd
have to first find out in what stage the problem occurred, and then
decide which directory to switch to.

There's also the issue that the final directory used by make bootstrap
should be the same as that used by make all.

All in all, I don't really see moving directories around is such a big
deal.  And faking the debug info stored in the object files could very
well lead to harder-to-debug gcc builds.

> and is the main obstacle to moving bootstrap to the top level.

I fail to see why.  Care to explain?  Maybe we can find a better way
to do it than what you have in mind.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


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