[PATCH] Don't hardcode target dependencies

M.Canales.es macana at macana-es.com
Thu Mar 15 11:20:02 PDT 2007

El Jueves, 15 de Marzo de 2007 00:26, Dan Nicholson escribió:

> Yes, I think it should be possible without a major altering of the
> code. In my mind, the way to do it would be to require root privileges
> then drop them with su $luser -c where necessary. There's the syntax
> issue where the su argument has to be wrapped in "", but I think this
> should workable with make functions.

The change that made we lost the "make 068-gcc" functionality (for example) is 
not related to under what user the master make is launch but due on how many 
times we are doing su to $luser or entering to the chroot jail.

The inner make invocations was implemented to can do "su - $luser -c" only one 
time to build temp tools, to can enter to the chroot jail only one time with 
the first chroot command to build the final system, and to enter another time 
with the second chroot command to instal bootscripts and kernel.

And that is exactly what the book expect: that commands should be run only one 
time in a linear by-the-book build.

Thus the question is: is there any other way to implement the "su/chroot only 
one time" requeriment that could allow have again the "make any_target" 

Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org

More information about the alfs-discuss mailing list