Re^4: Source files going into perl interpreter during compilation

Have you tried make 2>&1 > make.log?

At least in bash, the redirections must be switched (as shown in bash):

make > make.log 2>&1
[download]

Comment on Re^4: Source files going into perl interpreter during compilation Select or Download Code

Replies are listed 'Best First'.
Re^5: Source files going into perl interpreter during compilation by buntyshubho (Initiate) on Jun 22, 2011 at 13:40 UTC
This is perfect...switched redirections do work. I wasn't aware of this at all. Now, I have got all the #warning messages in a log file, sizeof(logfile)=19000+ lines. I can easily parse it using perl itself. A hackneyed and definitely not elegant approach, but definitely seems to work. Thanks a lot monks. If there is any other solution that one can think of, it'll be great for the sake of sharing knowledge UPDATE: Also, like BrowserUK said, it is using -O2 optimization and hence static char* are not being displayed using "strings" in any .o file. But simple char* are displayed. This still seems confusing to me. I guess I might have to read up a bit on compiler optimizations.	[reply]

Replies are listed 'Best First'.

Re^5: Source files going into perl interpreter during compilation
by buntyshubho (Initiate) on Jun 22, 2011 at 13:40 UTC

This is perfect...switched redirections do work. I wasn't aware of this at all.

Now, I have got all the #warning messages in a log file, sizeof(logfile)=19000+ lines. I can easily parse it using perl itself. A hackneyed and definitely not elegant approach, but definitely seems to work.

Thanks a lot monks. If there is any other solution that one can think of, it'll be great for the sake of sharing knowledge

UPDATE: Also, like BrowserUK said, it is using -O2 optimization and hence static char* are not being displayed using "strings" in any .o file. But simple char* are displayed. This still seems confusing to me. I guess I might have to read up a bit on compiler optimizations.

[reply]