On Tue, Aug 24, 2010 at 06:18:32PM -0400, linux fan wrote: > On 8/24/10, [email protected] <[email protected]> wrote: > > > > However, I'm confused. The error occurs on my screen with "make > > install." Should I have used something similar to "make install | tee > > LogFile.txt >2&1" to trap the error? If I do so, LogFile.txt is > > extensive, but omits those lines. What have I done wrong in trapping the > > error to text? > > When piping, I use something similar to: > make install 2>&1 | tee LogFile.txt > > I think that puts 2 and 1 together before it gets to tee. > That way, both stdout and stderr go to screen and to LogFile.txt. > I don't know if it's right, but it seems to work for me.
I do the same, but packages can get creative with where they write to - I've seen output from glibc (can't remember if it was test, or locales, or something else) on my screen, and not sure if I've fixed it, so it's possible that mplayer does something different. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
