On Fri, 2007-03-30 at 18:55 +0000, Thorsten Glaser wrote: > Lothar Gesslein dixit: > > >But because HOSTCC is also set to be > >"someothercompiler", > > True, but… > > > lbin/gcc is never called > > … I wish this were true.
So the lbin/gcc is there for the case that neither HOSTCC nor CC is honorated in some buildscript? Is this a real bug somewhere? Won't it be easier to just fix the buildscript then? I think such constructs add unneeded complexity and abstraction. I'd even kick the HOSTCC line out of the prereq and just set HOSTCC to CC in the Makefile directly to have CC honoured on every make (and not only after a make prereq). I do not know any buildsystem that needs such a construct. We are not doing anything special here, just compiling. Maybe i'm too naive at this point? > >Case c) CC="something gcc". We prefix gcc with some other programm, e.g. > >ccache. lbin/gcc is a script which executes "something gcc" (where gcc > >is the real compiler, because of the PATH definition). HOSTCC is also > >set to "something gcc", but this time gcc is lbin/gcc. So this expands > >to "something something gcc" beeing called as the compiler in the end. > > Hmm. The “immediate trivial” approach would be to set HOSTCC to lbin/gcc. > Would that be facile or do I overlook something? (Sorry, I just finished > my first week of major work and am likely to produce lots of thinkos.) I thought of this, it should work. Although this is no nice solution, imho. > > >Please object. > > I hereby do. Thanks. =) Bye Lothar _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
