Error logging during make check

English Programming/Scripting
#1

Hi,

I am building PPL-0.10.2 32 Bit and running make check at the moment. I need to log the errors (if any) to text file. How do I do that.

I know I can copy paste the output from terminal but I want automation.

Best,

Dave

#2

The following line sends all text and errors to a new file called log_file_name. If log_file_name is a variable in a script, it would have a $ sign in front as in $log_file_name where somewhere in your script you said log_file_name=actual_log_file_name:

make > log_file_name 2>&1

To append to an existing log file, use this method:

make >> log_file_name 2>&1

Is that what you were looking for? This works for most all terminal commands, not just make.

Thank You,

#3

Hi,

I am building multilib in chroot environment.

Please correct me if I am wrong-

make > /mnt/build/log/ppl-make-check 2>&1 check

OR

make cat > /mnt/build/log/ppl << "EOF" check

I prefer the 2nd command but not sure how to make that correct.

Best,

David

#4

@jdmcdaniel3,

I guess the one that you mentioned is correct.

 make > /mnt/build/log/ppl-make-check 2>&1 check

Let me know if it is correct for chroot environment.

Best

#5

I am not familiar with the command(s) make check. Give me the command line(s) that you use that works without logging anything and let me try to adding the logging to that.

Thank You,

#6

On 2011-01-01 08:06, jdmcdaniel3 wrote:

> Code:
> --------------------
> make > log_file_name 2>&1
> --------------------
> To append to an existing log file, use this method:

I prefer this:

Code:

make [options] | tee log_file_name 2>&1

because you also see them in the screen.

If the OP is building inside a chroot, notice that the outside /mnt is not
accessible, and that all programs used must be accessible inside (copied).

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#7

OK, I tried several things and this is what worked -

mkdir /mnt/clfs/log
make check 2>&1 | tee -a /mnt/clfs/log/ppp-lib64.log

2>&1 are basically data dump.

#8

Carlos,

I guess its better to put dump 2>&1 before pipe. Anyway I will try that out soon (but not for gcc), its a devil.

Best,

David

#9

On 2011-01-01 16:36, avenuemax wrote:
>
> OK, I tried several things and this is what worked -
>
>> mkdir /mnt/clfs/log
>> make check 2>&1 | tee -a /mnt/clfs/log/ppp-lib64.log
>
> 2>&1 are basically data dump.

2>&1 is to add or redirect the errio to stdio, which is the only one that
goes through the “|” pipe.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#10

Thanks Carlos.