Code: Select all
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k
Code: Select all
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k 2>compile_errors.txt
Sorry but that has just got me totally confusedJoe Schmoe wrote:Simple redirection ought to work - many example command lines have already been posted here.
But I suggest that for this and similar problems, the "script" approach is better. The script command allows you to run a command line (or just an interactive shell) normally, with all input and output visible, while saving all of the terminal dialog to a file. There is a (more or less) standard Unix command called "script", that you can read about with "man script", that is basically a proof-of-concept implementation of the idea.
However, I find that the built-in command has some quirky limitations, so I prefer this implementation, in Expect, which I use all the time:
begin 644 Script.zip
[email protected]````!38W)I<'155`4``[BDJS15>```4$L%[email protected]`````!``$`00```,8!````
The Pi has certainly got my mind churning It shouldn't be so bad after a while as I used to be very involved in Linux but a very, very long time ago with Linux 0,x.x and 1.x.x, helping with LSI Logic SCSI driver development. Its just a real problem trying to remember how to do even the most simplest of things at the moment. Feels like being back at primary school.Joe Schmoe wrote:I would start out by reading "man script", which will give you the basic idea - and you can start playing around with the built-in "script" command.
Then, I would suggest "man uudecode" and this will lead you to figuring out how to decode my uuencoded post (which is necessary, because the "Upload attachments" functionality is busted here). Then you can unzip the resulting file (Script.zip) and get the Script command. Then you can figure out how to put that in a file and make it executable, then finally all your efforts will be rewarded. And, you will learn about the wonderful "Expect" command as well.
All in the spirit of what the Pi is all about, doncha know...?
Thanks for that. Just wasn't sure if redirecting the output of make was valid or not.jmacey wrote:if you do
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k 2>compile_errors.txt &
This will detach the build from the console and make it run in the background (the & does the detach) you can then follow the output of the error file by doing
tail -f compile_errors.txt
( use CTRL + c to exit the tail program).