Gerard Beekmans wrote:
> The following command in chapter 6's glibc:
>
> make -k check >glibc-check-log 2>&1
>
> Could stand with a bit of modification so it outputs to both the
> screen as well as the log file. As it is, there is no output on the
> screen at all, which is so unlike any other
Randy McMurchy wrote:
It can only slow you down (sometimes significantly), and there is
I tend to look at things from the other way around: if you are one of
few who is slowed down by this (remote builds), then you probably make
other changes already since most every single other command in t
Gerard Beekmans wrote these words on 05/27/06 19:48 CST:
> Could stand with a bit of modification so it outputs to both the screen
> as well as the log file. As it is, there is no output on the screen at
> all, which is so unlike any other make and make check run from the book.
I'll agree that
The following command in chapter 6's glibc:
make -k check >glibc-check-log 2>&1
Could stand with a bit of modification so it outputs to both the screen
as well as the log file. As it is, there is no output on the screen at
all, which is so unlike any other make and make check run from
