This is the mail archive of the gcc-bugs@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]

[Bug bootstrap/30541] Top-level should pass GNATBIND, GNATLINK and GNATMAKE variables down



------- Comment #13 from paolo dot bonzini at lu dot unisi dot ch  2007-01-23 14:55 -------
Subject: Re:  Top-level should pass GNATBIND, GNATLINK
 and GNATMAKE variables down


>> True, they seem to be unused, but it's better to be consistent; for the same
>> reason I prefer to pass GNATLINK down too via flags_to_pass.
> 
> Not only "they seem", but they ARE unused.  [...]
> So I see no reason to add GNATLINK here really.

I meant they seem to be unused because we always rely on the 
GNATMAKE/GNATLINK passed by a higher-level makefile.  It's good to write 
in the makefile the variables that you use -- even if they are always 
overridden.

> Now, gnatmake is also needed because of some support tools, but logically,
> these support tools should only be built once before bootstrap starts, in
> order to generate automatically files.

Note that the exact same steps are followed in all the three stages. 
stage1 does not have *anything* magic in it.

If gnatmake is used in stage1 to build support tools, the same tools 
will be built in stage2 (using gnatmake) unless these tools write in the 
srcdir.

Paolo


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30541


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