|
From: Andrzej O. <an...@ma...> - 2009-01-13 15:57:33
|
Oliver Niesner: > I had the same problems when i tried to compile the development release. > > It is very useful to set the following option in your .config file: > > CONFIG_DISABLELOGGING=y (yes, the naming of this option is extremly weird!) > > It is confusing, but this ENABLES logging during compile. Enables to console... but disables logging to files in directory /build/tmp/LOGS/... I think, cause of this is named DISABLELOGGING > This is important when you have to answer some questions about new Kernel features, > which causes the buildprocess seem to "hang" because you don't answer the question(s). I solve this looking on compilation process on one PuTTY screen and when "hangs", then on second screen I display according log file, i.e. tail -f /usr/src/lfssystem/build/tmp/LOGS/build/grsecurity and answer on the first screen to the questions on second :) Additionally I have logs in files and I can reference to this files, when some phase fails. > After a complete remove of my lfssystem and enabling the above option, my setup build > nicly and i have now a fresh DL-1.3.7 ;-) > > Hope that helps, Thanks, Oliver. This time problem was solved by the hint from Heiko. This new Heiko option "CONFIG_GCC_CPU=" was by default set empty in .config Setting it to the CONFIG_GCC_CPU=i586 solved this problem and full build process ended some minutes ago. Now I run make install. Regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |