Re: What commands will compile a Kernel?
Thanks for the suggestion Paul.
Your command use a csh method, '>&', of associating stderr with stdout, where bash uses the '2>&1' to do the same thing. I prefer 'less +F' to accomplish the 'tail -f' so that I can move around the output when I'd like to.
I started using multiple 'make's with intervening '&&'s because the output from 'make oldconfig' suggested it. I didn't question or investigate why multiple 'make's, rather than a single make with multiple targets, were recommended. I did understand that 'make' can use 'include' files and that those files could conceivably be changed by any 'make <target>', so I simply followed the recommendation.
So does the 'make' procedure for building kernels use 'include' files and, if so, do any of the make targets affect the included files?
I'm happy to continue building as I have, but I'd like to be sure that it's a 'correct' way to build.
At 01:15 PM 1/20/99 -0500, you wrote:
>>
>> Peter Mott wrote:
>> >
>> > Is the following from a bash shell prompt a good way to do it?
>> >
>> > (make dep && make clean && make boot && make modules) > make.log 2>&1
>> >
>> > Unlike separating commands by ';' the '&&' makes it stop if an error occurs.
>>
>> That is a really cool way to do it, however the redirection dosn't work
>> very well. Does anyone know where the output of make goes, I would like
>> to be able to review the process. Now to find out what hardware I
>> actually have?, ;>).
>>
>
>try this:
>
>make dep clean boot modules >& make.log &
>tail -f make.log
>
>it will log it to the file make.log and still display it to the stdout.
>
>Paul
>
>
>--
>To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
>
Peter Mott | mailto:mott@mathworks.com | Voice: 508.647.7375
| http://www.mathworks.com | FAX: 508.647.7002
PGP fingerprint: AAB3 CC97 3045 15F1 A9CC ECA2 0207 FB0A 0997 8F31
Reply to: