Question

I have a large codebase that I’ve been tasked with porting to 64 bits. The code compiles, but it prints a very large amount of incompatible pointer warnings (as is to be expected.) Is there any way I can have gcc print the line on which the error occurs? At this point I’m just using gcc’s error messages to try to track down assumptions that need to be modified, and having to look up every one is not fun.

Answer 1

I’ve blatantly stolen Joseph Quinsey’s answer for this. The only difference is I’ve attempted to make the code easier to understand:

For bash, use make 2>&1 | show_gcc_line with show_gcc_line the following script:

#!/bin/bash
#  Read and echo each line only if it is an error or warning message
#  The lines printed will start something like "foobar:123:" so that
#  line 123 of file foobar will be printed.

while read input
do
    loc=$(echo "$input" | sed -n 's/^\([^ :]*\):\([0-9]*\):.*/\1 \2/p')
    len=${#loc}
    file=${loc% *}
    line=${loc#* }

    if [ $len -gt  0 ]
    then
        echo "$input"
        echo "$(sed -n ${line}p $file)"
        echo
    fi
done

This was partly because I did not like the formatting of the original. This only prints the warnings/errors, followed by the line of code causing the problem, followed by a blank line. I’ve removed the string of hyphens too.